Member-only story
Featured
8 Programming Concepts That Look Useless Until Something Breaks
Some programming ideas feel academic only because you haven’t yet seen the production failure they help prevent.
If not a Medium member ? Click Here
Some programming concepts sound unnecessarily formal the first time you encounter them. Why name an invariant when everyone already knows inventory should not magically disappear? Why make an operation idempotent when it is only supposed to run once? Why worry about backpressure when the worker is processing jobs perfectly well?
Under normal conditions, those objections can appear reasonable. Then two workers update the same record, a server completes an operation but its response disappears, producers become faster than consumers, or an object changes after another task has already assumed it was stable. The terminology suddenly stops looking academic.
A surprising amount of programming theory is really failure knowledge compressed into a name. The definition is usually the easy part. The more useful question is what kind of bug becomes possible when the concept is missing.
That is where these eight ideas start making sense.
