I believe everyone is familiar with the popular saying that one can have 10 years of experience or 10 x 1 (the same) year of professional experience. If you don't get the difference - it's all about being exposed to new experiences (that can be substantial in spurring your personal...
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 what's accidental complexity, how to measure & manage complexity, etc. The...
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 X X starts his software development career. X doesn't know much about the job market, local companies, their specifics - he's fresh & probably doesn't even know...
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 the specific idea of a sprint goal. I believe such...
Let me start with some observations: 1. 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 MVC-style app programmers listening about data serializer replacement or memory...
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" - which is another topic I use to share my thoughts...
