Fakes Over Mocks
A fake implements the same contract as the real thing, which makes tests easier to read.
Author
Ada writes about software craft and the history of computing. She keeps notebooks full of diagrams, half-finished arguments, and questions worth following.
17 stories Software DevelopmentThe Story of Computing
A fake implements the same contract as the real thing, which makes tests easier to read.
Lovelace's table of operations shows how a mathematical procedure becomes a sequence a machine can follow.
Good seams make behavior testable without turning the test suite into a wiring diagram.
Her notes on the Analytical Engine imagined a machine that could compose music as readily as it could solve equations.
The history of memory is a history of making the invisible reliable.
Packet switching replaced the idea of a dedicated line with a shared, adaptive path.
Errors carry meaning. Wrapping them well is a form of documentation.
An interface should describe the smallest useful behavior a caller needs.
A system that cannot explain itself is hard to operate, no matter how clean the code looks.
The network changed the computer from a room-sized tool into a place where people could meet.
Memory was once a room full of delicate hardware, and every bit was an engineering achievement.
Before there were computers to run, there were people imagining what instructions could make them do.
Production is not a substitute for tests, but it is a place where hypotheses meet reality.
The most durable architectural choices are the ones that make unwanted dependencies hard to add.
Maintainability is less about clever patterns and more about the daily choices that keep a codebase legible.
A thread about the first programmers, the machines that learned to remember, and the networks that connected them.
A thread about small interfaces, clear boundaries, and the everyday habits that keep a codebase healthy.