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.
Breaking rocks like it's 1979 Some good analogies keep haunting me for years :) One of them I've heard from Liz Keogh [http://lizkeogh.com/] some time ago - I don't remember the exact event, but I'm sure it was live, not recorded...
We 'like' to put blame on factors that (in our opinion) lie beyond our control - stone-carved deadlines, outdated legacy, unimaginative Product Owners who always dump tech debt-related work items into abyss of Nice-To-Have. Some call it 'victimship' & it's all about giving up...
When I was starting my first paid job (as a software developer) success definition was quite simple: deliver pre-defined scope in pre-defined time (budget) & make sure that bugs don't break the general usability (you can call it a loose quality criteria ;>). A lot of things have...
Well-built service API may be a game changer. In both client-server & server-server scenario, especially if you're following the latest trend of building fine-grained, loosely coupled (micro)services. I've seen several attempts, in different languages, for different domains & running on different platforms - regardless of...
Who of you hasn't heard that from a more senior colleague / boss? > Software development hasn't truly changed at all in past 5/10/20/30 years. It's about all the same patterns / models / approaches that keep having their highs and lows alternately in...
Let's start with a short quote from the book I'm reading at the moment (recommended, good stuff): > "In good organizations, people can focus on their work and have confidence that if they get their work done, good things will happen for both the company...
