Topic: Standards
2026
2025
-
Book Club 8&9/2025: Async
Not the keyword, but asynchronous communication. It just seemed that 'Async' as a title was more interesting. -
I Like Petite-Vue
Simplicity is good, focusing on what's necessary is better. -
Book Club 4&5/2025: Incidents and Resiliency
Thinking more about responding to and preventing incidents
2024
-
It's Okay to be a Bit Techy in Your Gherkin
Gherkin tests are meant to be an abstraction over the code of automated tests to facilitate collaboration by all stakeholders, but that shouldn't mean that we banish any technical whiffs from them. -
Intuiting Jevon's Paradox
On the unintuitive pattern of resource consumption and how it relates to software engineering. -
Three Laws
Some 'folk laws' that are commonly known but seldom applied. -
Using Interfaces
I'm on a quest to make it happen less -
It's Better to be Consistently Incorrect than Inconsistently Correct
On consistency in code and what it means for something to be 'incorrect' -
Develop Effective Coding Standards
Bad coding standards are worse than no standards, and even good standards are sometimes unnecessary. What's the utility in coding standards, and what makes a good one? -
Four Deeply-Ingrained C# Cliches
There's a lot to love about C# and .NET, and there are some things that I don't love as much. Then there are four bad habbits that are so deeply ingrained they've become cliches within our codebases. -
Eight Maxims
A few principles for thoughtful software engineering. -
Just Use PostgreSQL
With a vast and growing ecosystem of database systems, data models, patterns, and paradigms, choosing the right one can be a long and complicated process. I prefer a simpler approach: Just use PostgreSQL.