Teams & Culture —2 min read
Why I don't like the "Tech Lead" role

The "Tech Lead" title is too often (ab)used as a way to "lord it over" people who are "less technically capable".

Teams & Culture —2 min read
Book recommendation: Team Topologies

I read most of "Team Topologies" on a flight to Madrid, and was able to immediately begin to put it to use.

Hiring —1 min read
A simple way to improve your technical onboarding

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

Software Delivery —1 min read
Manual deployments are a false safety net

“Whether a human is involved in pressing the deploy button or not, you are going to deploy a bad update eventually.”

Teams & Culture —1 min read
"Process" isn't a dirty word

"Process" gets a bad rap these days. Claiming you don't have a process is like claiming you don't breathe.

Teams & Culture —1 min read
Responsibility without authority is just janitorial service

If your task is to keep things tidy, but can't enforce the use of a tidy practices, you're a janitor.

Teams & Culture —1 min read
Context matters

Advice is never universal. Context matters.

Teams & Culture —1 min read
Work as if your team is quitting

Nobody stays at a job for ever. Be prepared for your colleages to leave.

Teams & Culture —2 min read
The efficiency of creativity

Software development is, in some sense, all about efficiency. Except when computers are used for entertainment (gaming, for example), pretty much their entire reason for existence is to make certain tasks more efficient. When we write software, we’re generally doing so with the purpose of automating, or simplifying some task that in some way, a human, or other less-efficient machine might be doing. Certain types of developers dedicate large parts of their careers to making the development of software more efficient.

Teams & Culture —1 min read
Reader question: Should we have a bugfix team?

Fellow reader Anita Kalmane asked: “What’s your opinion on having a separate team who is fixing bugs?” I want to share my response, slightly edited for brevity: I think it’s a terrible idea, except maybe as a VERY short term measure in an emergency. The three biggest reasons: It teaches the team producing bugs that “bug fixing is someone else’s problem.” It has the bugfix team working without proper context. Usually companies that do this put the “least skilled” (however they determine that) people on the maintenence/bugfix team.

Teams & Culture —1 min read
Resistance is expected

Don't take resistence to your great ideas personally. It could mean that you're onto something.