Are you worried that all these little classes and interfaces are going to destroy your system’s performance? Maybe. More often, however, the bottlenecks are caused by bigger classes and fewer interfaces causing duplication in the design.

A concise guide for going from nothing to a working nodejs environment on Linux environments.

How does one accept user input from stdin in a Java application when running it with gradle run when using the Kotlin build DSL? Here’s how!

Some programmers try TDD and feel blocked right away. “How do I write a test for code that doesn’t yet exist?!” I remember how it felt and what happened when I tried anyway.

If you want the full power of your trusted text editor to compose and edit long shell commands, then you can have it!

The integrated tests scam goes beyond “merely” making tests slow and brittle. Sometimes they render impossible an otherwise straightforward test.

Programmers get into trouble when they try to use one set of tests to check their code and someone else’s framework. Clarifying the intention of the tests and isolating these two kinds of behavior from each other tends to lead to better results overall.

Revised one of my earliest contributions to the evolutionary design community: abstract test cases and their evolution into contract tests

I started out by wanting a Nunjucks filter to reverse a collection of posts, from which I would later “take 10”, but then I realized I could simply program by intention.

We removed duplication as part of fixing a defect. Doing this helped us see more clearly both how to understand and fix the defect.

In the process of refactoring an 11ty configuration, I ran into an error message that I had to work hard to understand. Fortunately, microcommitting made it relatively easy to diagnose and fix the problem.

Writing “too many” if conditions can cause problems in code, but I think we’d all feel better understanding why this might be the case, rather than merely repeating received wisdom.