Most big corps just need a lot of decent coders to pump out a lot of business logic and UI. AI is definitely going to be able to do that with some basic human validation along the way.
The problem with the validation part is that the human has to go through all the code written by AI. Guess what, understanding someone's code takes almost as much effort as writing the code yourself. Therefore you require just about the same amount of human beings verify AI's code.
Not enough time to even understand the requirements of a 40h job.
10h would be
minimum.
Unless you are just checking that the style guide is correct and obvious
missed null checks.
For this reason I feel code
reviews are a bit silly and pair programming is way better (pairing with a mix of sync and async work) but that is an aside.
In addition a code review being short is usually because the coder and reviewer are both very competent. Once AI
enters the chat the reviewer needs to look very closely at every line.
Code reviews are more of a formality, a pointless one. There's little to no value in one code reviewing a piece of code without the background business problem being solved by it.
Sure but a “superficial” review is what most corps currently run on. Certain crucial code gets looked at more throughly. If there are any bugs QA catches it.
It’s going to be the same with AI. It pumps out a lot of code. Human does spot checks and probably uses other AI to help with the code review. A real human does the really hard, critical code directly. A more robust QA team makes sure it all works.
I think you are right in the near future but not today. I don’t think we are quite there yet with AI but the pace of improvement is breathtaking and producing code (and more generally “logic” which could be code but also machine code, system design, LLM prompts and so on) is such a pot of gold the AI companies will go for it.
Yeah thats because then they don‘t really look at it and certainly don‘t really understand it.
In some way reviewing code is more complicated and hard than actually writing it.
I really like the „reverse centaur“ metaphor by Doctorow regarding the automation AI will bring us - humans having to double check the stuff AI wrote for correctness in AI pace.
At a big corp: 90% of my job is talking to various people to figure out what we want to code, who has to approve it, who I have to coordinate changes with, etc. AI can currently _maybe_ do half of the 10% that's left, with good amounts of supervision.
The supervision is also difficult to do unless people get enough experience actually doing the job, so expect it to take even longer to get people to verify the code once it's written by AI. This is the same concern people have about autonomous driving. If you let the machine take over, then you'll be out of touch when you're called on to do the real tricky bits of work.