Now, if the sales guy needs a feature by the end of the month, it’s possible that—with the help of AI—you could actually do the implementation in the compressed time frame. Not only that, but you could certainly instruct the agent to do it while following your initial design and high standards for coding, right? Sales deadlines may never change, but the time required for a software development team to implement a feature has compressed dramatically in the last year.
And that raises the question about the code itself. If, as I’ve written, the code doesn’t really matter to humans anymore, then can we even have such a thing as a big messy codebase? If the agent can understand your entire codebase, make changes, fix bugs, and add features with ease, what, then, is the problem?
When the CEO backs the sales guy and says “build that feature by the end of next week,” is that really a problem anymore? If you care about the code, then you can have your agent write clean, maintainable code that is up to your standards. If you don’t care about the code because you’ve abstracted it away behind the agent, well, then your agent can probably build that feature in short order no matter what paradigm you use to code.
