-
Engineering involves compromises and trade-offs. But is it a good idea to trade-off quality of code for time?
-
As you gain more experience, you realize that there’s more to writing software than just the technical.
-
Reading code is a necessary skill— most of a professional software engineer’s time is spent reading code. But how do you write readable code?
-
On documentation, the phrase “RTFM”, and writing good documentation.
-
Confidence, criticism, and why code reviews are hard.
-
One thing I’ve learned early on is that commit messages are important; it’s the one thing I always read first when reviewing code to understand the context of a particular change.
-
Thoughts on Emacs and the other tools in my repertoire.
-
I’ve come to realize that a lot of design and architectural decisions are a fight against entropy, and it’s a never-ending battle.
-
Freelancing and consulting work isn’t my cup of tea, but I’ve learned a lot from it.
Musings about the theory and practice of writing software. Not
necessarily code-focused, but may occasionally have code.