A few weeks ago, we (myself & my two friends - Tomek & Wojtek, as a part of a community called CTO Morning Coffee) hosted an online X Spaces session on Domain-Driven Design (DDD). To be clear, this wasn't supposed to be an intro session; quite the contrary....
Many people who've never seen high-performing teams in action (I mean genuinely high-performing, not just the ones who self-claim they are ...), assume that all that you need to form such a team is: * assign them a mission (they could identify with) * grant them a sufficient level of autonomy...
I've used many personality assessment methods & tools in the past. Gallup SF, Transactional Analysis, OCEAN - that sort of stuff (& more). I'm not a professional behavioral psychologist (of course), but I thought nothing would surprise me regarding the qualification of personality types. Yet, I&...
It's one of the lessons I've learned the hard way: there's no other resource valuable more than your own time. Why so? * it's hard-capped * it's not transferable (my time isn't directly exchangeable with your time, at least in...
I bet that nearly everyone in the software-crafting industry has heard about YAGNI [https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it] ("You Ain't Gonna Need It") principle. But what about TAGRI? TAGRI (which is nearly as old as YAGNI) stands for "They...
There's an interesting trend of expanding the range of work products developers produce as the outcomes of their work. In software development prehistory it was just functional code (one that's supposed to provide business value directly). After some time automated tests have joined it - as...
Disclaimer: the idea of immutable code ain't mine - I've read/heard about it somewhere (can't recall precisely ;/) some time ago & it sticked with me. Code maintenance is already a huge problem & it won't get any better by itself. Software...
One of the things I'm truly & fully proud'n'happy is the way I'm managing my own self-development. I never had problems with: * declining motivation * making decisions on what to do next * lack of focus * burning out * losing ability to reach the state...
In 2016 pretty much every commercial software system built with modern tech is a distributed system. Yes, we all build distributed systems these days. Obviously, the term "distributed" is very spacious - I'm not saying we're all creating stuff like eventually consisted, sharded data...
It's a real grind, what we do here In real life, software delivery rarely is a piece of cake - writing actual, production code doesn't resemble "happy path" tutorials, industrial domain models are much more complex than "Animal -> Dog" hierarchy,...
Some time ago I had an interesting discussion with one of my colleagues regarding what is the typical thing that goes wrong when software delivery project turns out to be unsuccessful. Many of the reasons we've identified were not really revealing: * new, unknown, bleeding edge, unproven technology -...
