How to stay sane when you have an infinite amount to learn
I was having a conversation with some younger colleagues today about early-career development.
Ben’s Guide to Software Development
a thousand little improvements
Live Last read · last published · next check
Latest posts
Code is not (just) a liability.
It's more complicated than that.
AI is a lot of fun
The most positive thing I can say about “AI” coding tools is — and I mean this sincerely — that they are a lot of fun to play with.
Some Questions Driving Empirical Software Development
empirical (adj.)
Structure Eats Behavior for Breakfast
Prioritizing software defects
Reasons not to write bugs
What's 0.1% worth?
Service Asymmetry
Imagine we're the programmers responsible for building a software service.
Steps Under the Microscope
We change a software system by taking many small steps to get from our current state to our desired state.
A Taxonomy of Testing
Unit vs. system, manual vs. automated
How I make decisions
Here’s how I actually make decisions when programming.
Diamond Design, Part 2
Hello and happy new year!
Diamond Design, Part 1
An alternative to the dreaded `utils` folder
The Zero-Bug Rules
There once was an Old West town called Two Dudes.
Readme-driven development
My first forays into programming, in middle school and high school, were in the domain of computer games — written in Visual Basic, of all things.
Entrypoint Document
How to find what's important
Walking Skeleton
How to begin
Great code is CEVICHE
The title of my work-in-progress book is Process to Processes. That’s because software development starts with a human process (team structure and development workflow) and ends with computer processes that effect some desired behavior. The first process fully determines the nature of the second.
Why make software better?
Reintroducing Process to Processes
Stack, Queue, or Shrug?
How to navigate a mess
Code Quality: Hidden Costs, Unexpected Benefits
Cross-posted from benchristel.com.