So I constantly had to fight management about paying my people when well I moved to IT. Management saw them as replicable by anyone that knew the software we used. I saw them as domain experts that knew HOW we used the software we used, the software was secondary to knowing the company (and basically how every job was done in the manufacture of a 30,000+ part product). When I was a dev, we were partnered with industry domain experts so that we understood how the software was implemented to a level that 'self documenting code' never will.
Software is a cog. You're code can't be that self documenting to become domain expert for the domain it is trying to fill. That's like documenting how to train for a marathon by looking at running shoes.
Unlikely. LLMs only understand the code they're looking at, but not in the context of the complex interactions. E.g. LLMs won't understand how a particular line of code fixed a system outage that occurred last year.
I mean, it might be able to, as could a junior software engineer. That's besides the point.
It's rare that just reading the code will actually capture the spirit of what it means, that you could skip the step of asking the folks who wrote it why things are the way they are or the step of experimenting with it yourself to get a feel for it.
Or in other words, it doesn't really matter who reads the code. You still don't get to skip the knowledge building.
