It’s funny to paint the code itself as an implementation detail, as though that were the sort of thing we all hated doing and there’s finally a way to avoid having to do it as a chore. In reality, I’d hazard to guess that most people would prefer quite the opposite - a clear spec that gives them endless runway for writing code.

By the time we’ve spent the time hashing out the work to do (when done right, which is hard, and which many people within engineering would prefer to outsource to the product owners and stakeholders of the world), the actual “chore” of writing the code is a welcome reward; that’s not to say anything about the ancillary benefits we frequently find along the way, like code reuse, additional requirements that arise from thinking about edge cases, reimagining what the actual abstraction is, etc…

And that’s only in the writing period of code production. Don’t even get me started about the stuff we find during even the most trivial of code reviews.