A collection of 20 posts
One of the most valuable lessons I've ever learned (when it comes to building software) was: "Keep it simple, as simple (boring) stuff usually works best".It's usually accompanied with some sort of complexity consideration: what's essential (inherent) complexity and…
Read More
This article is about how finance-related decisions can lock your career development down if you don't understand what you're really paid for ... Reader, meet XX starts his software development career. X doesn't know much about the job market, local companies,…
Read More
I've always been praising the value of maintaining a stable rhythm (cadence) of the software delivery - frequent, regular, habitual, nearly continuous. That's why as a Kanban aficionado I've never minded the concept of a sprint - and in particular…
Read More
Let me start with some observations: the most popular tech meet-up talks are about the most hard-core, niche, infrastructure-level optimisations & techniques - while 97% people in the audience never encounters any practical scenario these apply to (e.g. web…
Read More
Quite recently I've shared my personal interpretation of "seniority" in tech (based on the concept of "leverage" - shamelessly stolen from Andy Grove ...). This term ("seniority") is frequently closely associated (as an enabler) to the role of an "architect" -…
Read More
Let's talk about "seniority" - but not in the usual way, in a context of career progression. I'm more interested in speaking about the "seniority" itself, regardless of specialty/path chosen, compensation, labels & position names. It's the kind of…
Read More