> It's somehow more tiring, reading complex plans in response to your guidance, and then making decision after decision.
replyThis is the world of a manager working with a development team hah. When writing the code yourself is it not the same? If you're writing the code by hand then you're still making the decisions and still having to plan and design. I mean someone/something has to...
Historically, we make systems to make these decisions - build a method to sort potatoes. Or build a method that can build a method to sort potatoes.
replyAi, as a cognitive technology, has the potential to climb that hierarchy.
Yes, current software developers need to make more decisions now. But that is just until the methodologies settle.
Then it is over.
If you think the hierarchy has a highest level, or that abstraction can only go "this far and no further".. I don't know what to tell you.
replyIf the AI is asking you questions and requiring you to make decision after decision, then perhaps it's a spec issue. I know I've written a good spec if the AI does not ask any questions and doesn't get anything wrong after implementing the user story.
replyYou're not wrong, but isn't that just moving the same amount of decision making to earlier in the process?
replyWhat is a spec but a collection of decisions?
reply