Are you a Go developer? Thinking of learning Go? Check out my new YouTube channel: Boldly Go!

There isn't a one-size-fits all solution, but it's important to consider revertable changes.

Even with long-running feature branches, you can merge something daily. A bug fix, refactor, or utility function.

The importance of backward compatibility often pops up in some surprising places.

As in alegebra, code (re)factoring doesn't change the meaning of an expression, only the representation.

A simple rename can save hours of time in the future.

Maybe strict TDD isn't necessary for experts, but it's still useful to learn.

It's not the red/green/refactor cycle. The important thing is working in short test/code or code/test cycles.

Write code as if every function is a doorway, and every reader of my code will always experience the doorway effect.

Yishai Beeri of LinearB discusses strategies to improve flow of PRs and code review with smarter tooling.

How can we unambiguously represent a password safely for shell, YAML, JSON, etc, and also know if it needs to be unescaped?