Developer Palate Series Part 1 of 5: The Spaghetti Test
Why AI Can't Taste Your Code
Robot chef tasting their creation
Last week my 6'4" son asked me how I know when spaghetti is done. "The package says 10-12 minutes," he said. I threw a noodle at the wall. It stuck. "But mostly," I told him, "you just know."
AI can tell you the starch gelatinization temperature is 55-85°C. It can calculate the perfect cooking time based on altitude and water salinity. What it can't do is taste that moment when al dente is just right.
Here's the thing about code: it has flavor too. That moment when abstraction tips into over-engineering? When a clever solution becomes too clever? When the architecture feels... off? That's your palate talking.
You've been developing this palate for years. Every debugging session, every code review, every "wait, something's wrong here" moment. You've trained on thousands of code samples - good, bad, and catastrophic.
AI can follow every design pattern perfectly. It can't feel when DRY becomes WET (Write Everything Twice would be simpler). It can't feel when elegant becomes complicated. It doesn't get that tingle when a race condition lurks in seemingly innocent async code.
Your ability to taste - to instantly know when code smells wrong - that's not being replaced. It's being amplified. AI handles the chopping and measuring. You decide if the spaghetti needs another minute.
That's your irreplaceable 10% -
[
Software Design: Tidy First?
90% of My Skills Are Now Worth $0
I tweeted about this yesterday & it blew up…
Read more
3 years ago · 187 likes · 49 comments · Kent Beck
](https://tidyfirst.substack.com/p/90-of-my-skills-are-now-worth-0?utm_source=substack&utm_campaign=post_embed&utm_medium=web)
the skills that matter 1000x more. That's what makes you the chef, not the recipe follower.