Well, I’d be spending that work on a re-usable platform / framework. So if the argument is “it’s as much work as doing the work yourself anyway,” then I think it may be worth it.
Same argument we had for building the SQL engine. It’s a lot of work upfront but maybe we can benefit from its functionality for long after that.
I wouldn’t be building a project-scoped work harness. I’d be building a work harness for projects.
Edit: downvote me all you want. The comparison to the SQL engine was a good one.
It’s about increasing the baseline of readily-available information, boiler-plate, test data, POCs… between the times (T1) that I have an idea and (T2) that I’m ready to start working on that idea. It’s not about having the agent do the work. Not at all. That’s a static benefit which is created once then reused countless times for the foreseeable future — like SQL.
Well, I’d be spending that work on a re-usable platform / framework. So if the argument is “it’s as much work as doing the work yourself anyway,” then I think it may be worth it.
Same argument we had for building the SQL engine. It’s a lot of work upfront but maybe we can benefit from its functionality for long after that.
I wouldn’t be building a project-scoped work harness. I’d be building a work harness for projects.
Edit: downvote me all you want. The comparison to the SQL engine was a good one.
It’s about increasing the baseline of readily-available information, boiler-plate, test data, POCs… between the times (T1) that I have an idea and (T2) that I’m ready to start working on that idea. It’s not about having the agent do the work. Not at all. That’s a static benefit which is created once then reused countless times for the foreseeable future — like SQL.