Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The way I see it the only jobs you are realistically automating (without full on AGI) are the CRUD and pipework jobs which are unambiguously explainable without a lot of context.

The difficulty/complexity in delivering software is mostly on having accurate domain knowledge on the problem you are trying to solve and how users or other machines in that environment interact with said software.

So again, unless we hit a landmark of a very outperforming AGI I think that much of the domain knowledge in many software 'niches' will be out of reach of automation.

That is not to say that many sub-tasks/boilerplate cannot be automated.



But you are missing the point that even a robot could code 90% of the boilerplate and leave it to someone with domain knowledge to check it through and possibly tweak a few bits.


Is that not a good thing? That’s the worst part of software development frankly, writing that grunt work piping code.


If you spend 90% of your time on boilerplate you’re already going to be “automated” out by a cleverer primate.


Great, i can review it then. I don't want to write boilerplate or tooling. It's a waste of my time.


GitHub Copilot is starting to do this for me for specific items.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: