Can only speak for my own project, but can give an example:
After an aquisition earlier this year I got the task of doing an SAP-Integration for the new company, last time I did this 5 years ago it was a 6 month task, but with the experience and skills ive gained since I estimated it would be a 3 month project (with or without AI, most work is just logistics, AI cant help much there).
In those 3 months I was able to not only integrate SAP but also deliver a completely modernised user-facing software for that integration. While I could have written that software myself in a vacuum it would have never been worth it financially, since it would have delayed the launch of the integration by 6+ months. Building the software post-launch of the integration would have easily taken 2.5 years at minimum.
But this is also basically a "spherical cow in a vacuum" scenario, where I was essentially acting as a solo dev, in full operational control of the project, with deep domain knowledge of the topic and an allready fully set up codebase that I knew perfectly while working down ideas I've had in my backlog for 5+ years.
> Building the software post-launch of the integration would have easily taken 2.5 years at minimum.
What you have said is correct, it lets you build software much faster. The question however is: is that software making money for the company? (Not talking about what you built but in general)
I think, with AI, companies are saying yes to a lot of things they would have said No to ik say 2020. And as a result realizing “just building it” is not the answer.
Previously your GTM team or Product team would say “If we ship some big project X, we unlock $Y in revenue” but now people are realizing that those projections were really more of a hope. So companies are spending so much more tokens and shipping so many more PRs based on hope but a lot of it just doesn’t turn into meaningful revenue, especially not in short term
Yeah, thats why I meant I was in a spherical cow-situation, this was a situation where we took over a company in the exact same field and I had 5 years of experience on which tweaks would need to be made to be able to rationalise away positions.
This sort of system only works with internal software and an unusual amount of data. If we were in the business of selling that software we could not have charged a higher price for the new version over the old, the tweak could only be unlocked because we were able to control staff hiring and staff onboarding fully to make use of the new changes.
And it quite possibly creates a huge risk for the company in the longer term, there is only one person who knows how that all works.
Honestly not super sure if that is more of a risk than it was pre-llm.
As part of the aquisition I got access to their previous codebase which was some sort of incomprehensible PHP monolith, with the persons who wrote that code long gone. Thanks to LLMs I was actually able to extract the core useful concepts (again, sufficiently deep domain knowledge that I knew exactly what to look for). Without LLMs i would have probably extracted the absolute minimum and let the rest rot.
There is no reason a dev of comparable skill and domain knowledge would not be able to do that for what I built here.
But that codebase was written by people, so you'd be well positioned to take it over. I wonder if the same would be the case if you were to take over a codebase that was written by AI.
By that point it might no longer matter though, but I suspect that such code would have a lot more exposed edge cases than one where someone actually thought things through before coding.