3 ms·
70%... By lines written? Or by time taken? There is a huge difference. Sometimes you spend days trawling old code, even older dependencies to discover adding a
by Roark66 2y ago
70%... By lines written? Or by time taken? There is a huge difference. Sometimes you spend days trawling old code, even older dependencies to discover adding a line may fix your problem. In the meantime you may've read hundreds of pages of docs, seen dozens of diagrams. Hunted people that moved between departments and "worked on this before" etc. Then after you fix it yours in charge of organising testing and deployment to cert/prod including representing the change in risk assessment meetings. Good luck using AI to replace this work.
- danpalmer 2y agoI'm talking about time spent. I completely agree that all the work you've mentioned is stuff that takes time and that AI won't replace any time soon, but I strongly doubt that it's the bulk of the work. I'm talking about the programmers that a friend of mine works with who take several quarters to produce a dashboard, or the entry level PHP jobs that make barely above minimum wage and sell custom websites and hosting to real-estate companies in small towns, or the outsourced programmers that other friends interact with, who spent ~10 eng over 2 years building a "PaaS" style system in shell scripts that no one in their company actually uses because surprise surprise no one ever thought to ask whether it was necessary or had the right feature set or even worked (but management paid for it). These people are spending a significant amount of their time coding, but they're not spending time automating, or improving the process for next time, and so the work they're doing is fairly trivial and is most likely to be impacted by AI.