Geek, agilista, blogger, codefella, serial reader. In the daylight - I navigate & lead software engineering. #lean #design #aws #elixir #analytics. I speak here for myself only.
> TL;DR - learning new programming language's syntax doesn't make you able to properly (& fully) utilize its potential as each language comes with something much harder to learn: its own idiomatic identity - unique expressive power that determines constructs & patterns strongly preferred (optimal...
> TL;DR - commoditization of agile methods have brought a shift in thinking about managers' role & leadership in general, industry seems enchanted with idea of servant leadership, self-organizing teams & Management 3.0. But ... in fact the most successful examples of leadership represent a category of "...
> TL;DR - time is the only resource we can't get back or recover, so I've perfected my way to optimise its (personal) utilization. But I've went too far - as it has appeared, over-tuning own life has several negative consequences I wasn&...
Part I can be found here [https://no-kill-switch.ghost.io/architecture-in-the-wild-business-process-orchestration-part-i/]. > TL;DR - maybe thinking in "processes" is a relic of traditional, policy-driven, hierarchical enterprise? Decentralised model, based on business events & reactions tends to have some advantages & seems to match modern architecture principles better....
.Disclaimer: by "architecture in the wild" I mean situations (I've personally encountered) where sheer reality surpasses known (& somehow theoretical) standards / patterns :) in a way that does not impose any obvious solution. It doesn't mean (usually) that everything is so utterly broken, in majority...
> TL;DR - educating a specialist takes time, money & effort - w/o a guarantee of final payoff. Maybe it's the time to get back to traditional apprenticeship model to secure educator's position & make job market more sane? On several occasions I'...
