Writing code is easily done, but identifying the code that ought to be available is what's difficult nowadays. Many experienced engineers are having a conversation regarding the capability of "taste" to be the most crucial ability of the AI age. "Taste" here doesn't refer to fashion. Instead, it’s about judgment. It is about being able to assess the AI output and understand precisely what’s inappropriate about it, the type of thing that will add up as technical debt, before it's pushed through. Why This Matters Right Now Junior-level AI virtually generates code for free thanks to AI. You can develop a feature immediately that would have needed an entire day to build. But being "functional" and being "ready to ship" are not equivalent to each other. The space amid those two terms is where skilled engineers show their real value. Or where they reveal they have been slacking off. Taste Is Not Vibes I am referring to taste, which is how to distinguish code that needs to be written.…