> In the end, the “shortcut” had cost her more time than if she’d just done the work herself from the start.
I had this same opinion on AI IDE Copilots about a year and a half ago. They were too nascent, and writing code manually saved me hours of debugging their buggy code recommendations.
Fast forward - today—IDE Copilots have grown leaps and bounds in its quality of outputs. They have real utility now.
It's important to note that - "This is the worst AI agents will ever be, it will only get better moving forward."
I'm confident these tools will keep improving and eventually create net productivity gains, including for the Excel use case you mentioned.
> In the end, the “shortcut” had cost her more time than if she’d just done the work herself from the start.
I had this same opinion on AI IDE Copilots about a year and a half ago. They were too nascent, and writing code manually saved me hours of debugging their buggy code recommendations.
Fast forward - today—IDE Copilots have grown leaps and bounds in its quality of outputs. They have real utility now.
It's important to note that - "This is the worst AI agents will ever be, it will only get better moving forward."
I'm confident these tools will keep improving and eventually create net productivity gains, including for the Excel use case you mentioned.