TL;DR - Sometimes I get an impression that there are people who got "promoted" to Senior Developer even before releasing anything to production ... Clearly the length of tenure is not the key determinant here, but neither should be the 100% memorizing of given framework's / library / language's full syntax. There are certain much important qualities that may be harder to assess, but in fact
TL;DR - These are not just great times to be a Software Engineer - it's even better to be a Software Engineering Manager. Plenty of open development opportunities help in shaping your own, individual professional profile. Physical world borders are far less constraining in that industry. True engineering expertise (& individuals who can apply it within whole organization) gets noticed & appreciated. And
TL;DR OSS has conquered the world, forcing even the biggest players of commercial software market to adjust their strategy to this fact. But the original idea of OSS has got somehow twisted in the meantime: everyone uses it, without feeling obliged to contribute. What is more, consumers expect flawless quality, but rewards for providing this quality are very ephemeral (so very few take
TL;DR Software Development technology adoption lifecycle is susceptible to the same rules that apply to any other high-tech. Market success is not guaranteed by sheer innovation, technical excellence or even product capabilities - it does require certain qualities, but also favorable market situation & adaptable product marketing (adjusted to cycle stage). In fact, vast majority of technology novelties we so adore (and already
Disclaimer: I'm writing these words just few days before the official release of Visual Studio 2017 RTM & about 2 months before the release of .NET Core 2.0. Hence you may find this post a bit pre-mature, but actually timing is on purpose - I'd like to make a stone-cold summary before all the marketing hype & another wave of rising hopes ...
TL;DR Some time ago I've declared my little, private war ... War against misleading, illogical & inconsistent depicting of solution architecture by people who either intentionally or due to their ignorance mix simple (yet very different) concepts i.a.: logical view, physical view, functional view. This is the post about this warfare ...
I believe many of you (the ones who work in large enterprise
TL;DR - the word "digital" became a real catch-all in 2016 - everyone wants to digitalize their business, w/o understanding what it truly means: no wonder that it attracts all kinds of impostors, slyboots & other types of consultants ;P - all eager to sell you a "digital" pig in a poke ...
Good wording is priceless. Well chosen brand tagline or catchy
_Disclaimer: this post is not intended to provoke or troll anyone. The idea isn't to present any language / paradigm as better or worse than any other. I have friends who prefer (& use on the daily basis) all the technologies mentioned below - I respect all of them as not only great guys but also top-notch professionals.
TL;DR - modern Functional Programming is
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 by design) in this particular language.
These are great times for being a software engineer. There are so many
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 "scoundrel leaders" - ruthless, narcissistic manipulators who subdue everything (& everyone) to their vision & style. Let's
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't aware of. Learn from my mistakes.
These of you who know me in person now that I'm 100% sane ;). I have
Part I can be found here.
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. WHAT IF we ditch BPM completely?
Is there a better way?
There are at least few scenarios that seem to fit modern