Keeping configuration in version control is highly correlated with software delivery performance.

If your application relies on serverless functions, often there's limited opportunity for "from an airplane" work.

If every engineer on your team cannot do _meaningful_ work from an airplane, your development environment is broken.

Given the choice between a video game or adding a feature to a hobby project, I often choose the latter.

Perl, Java, C++ are as hard for novices to read as a randomly designed langauge.

Simply adding a linter to your build pipeline is usually the simplest, cheapest single step you can do to improve code quality.

I've worked on a number of greenfield projects, but there's a problem: A greenfield project is only greenfield for about a week.

The only time less typing is more important than readability is on the command line. When writing code, readability wins by a mile.

As many of us begin to move back in offices, how can you ensure that you and your team can maintain this benefit, even if not in a physically isolated pace?

I'm a very fast typist. But that has no bearing on my ability to solve problems with code.

Code should have certain patterns and rythms that make it easy to read and understand.