Even in a static environment, improvement may slow down, but it doesn't have an upper bound.

Introducing a new technology usually means taking on new risk, so find some value that your new learning will provide to your boss.

Why are new joiners often quick to offer unwanted advice on how to improve things? Many "newbies" can't distinguish between core skills and company-specific skills.

The three (plus one) approaches I've used to change tech stacks in my career.

Somewhere, long ago, I learned of a technique I like to employ when onboarding new team members

Sometimes you simply cannot be ready before comitting.

I want to skip the debate about whether the 10x developer exists and tell you how to be one.

The first time I saw TDD demonstrated I rushed home to try it out. I wrote a few tests. I did a little TDD. And I hated it.