Why Bad Technique Shows Up Fast in an Espresso Shot and a Tomato
Most complexity in software is just cover for bad defaults. You see people building elaborate wrapper libraries with fifty configuration flags because they cannot state what their tool actually guarantees. Over at App Coding they nailed this: a useful software primitive should fit its explanation into a single sentence and then handle every ugly edge case under the hood without complaint. When an interface is tiny, you cannot hide behind architecture diagrams. The guarantees either hold during a crash or they do not.
It is the same reason why so many people ruin espresso. You pull an espresso cortado at a quiet counter, you look at the bottom of the portafilter, and you see whether you actually know how to tamp. Espresso Cortado wrote a breakdown on how water finds the weak spot in your puck, which is basically the hydraulic version of technical debt. Water is lazy. Push nine bars of pressure into an uneven bed of grounds and it digs a channel straight through the path of least resistance, giving you a cup that is bitter and sour all at once. You know the type who buys a four-hundred-dollar tamper to fix a prep routine that was sloppy from step one? Don't be that guy.
Image: MediaInstances.com
Minimal setups expose your actual skill level immediately.
Take kitchen knives. You wander into a specialty shop in Tokyo or Solingen and the wall of whetstones looks like an intimidation ritual designed to sell twelve different blocks of synthetic ceramic. Yet Sharp Knife points out that two stones a home cook actually needs come down to a medium sharpening stone and a fine finishing edge, or just one combo stone. When you sharpen on a single block of grit, you cannot blame the gear. You either held a consistent angle along the curve of the steel or you rounded the bevel into a butter knife. There is no middle ground.
Which reminds me of buying produce on the road. The street vendors in Mediterranean towns never try to sell you sixteen fancy toppings because a good tomato needs very little beyond coarse salt and decent olive oil. Put a cold, mealy tomato on a plate with salt and you get wet cardboard. Serve a ripe one at room temperature and the whole thing sings. Every single shortcut, from dull knives bruising the flesh to bad oil drowning the acidity, sits right there in plain view.
I have a terrible habit of adding third-party dependencies to side projects just to avoid writing sixty lines of tricky state logic. It is comforting to pile on abstractions because then a bug feels like someone else's fault. But stripping away the scaffolding forces you to face the fundamentals.
Less stuff leaves you with the truth.