sure, this is short-term because you still have people around who wrote (most of) the code and understand it
once you no longer have a good understanding of the codebase, you also don't know what to test and validate
AI is great at writing tons of tests; whether they're the _right_ tests is another question
I am struggling to come to terms with this personally. I was someone who really tried hard to make sure the nuts and bolts was good quality. Kept on top of language features, made sure not to use deprecated APIs that could expose security problems, etc
It wasn't just "to make the code more maintainable" or anything, those choices mattered, or felt like they did
Now it feels like everyone is saying "those choices don't matter, and never did"
Have I just been wasting my time and focusing on the wrong stuff for my whole career?
I'm going to ignore the using an actually broken API, and instead think about using a sub-optimal one.
Before, you tried hard to get it right first time, because it was a pain to change if it wasn't.
Now, that change is much, much easier. A task like "rip out this deprecated package and replace with a new one" used to be a LOT of effort but, if we're honest, not an awful lot of skill. Now its quick and easy.
Making the right product choices, or architectural decisions remains just as important, because they're still an absolute nightmare to change later, but the nuts and bolts much less so.
One thing I am still seeing is we STILL can't admit when we're wrong. We refuse to believe that we cannot think of everything before the code gets into production.
Really it's some core teams who do not have a 'sustaining' budget. They call themselves Services R&D.
For example they made a messaging stack with encryption, serialization, addressing, routing, etc. But it has a huge flaw in that there is a maximum packet size. The design is such that an app cannot implement chunking on top of the messaging. So there is no way to transmit data greater than the packet size or do any kind of data streaming. THere are 3 products now who are mandated to use this messaging stack but can't fit into the packets
It seems like a culture of 'deliver and move on' rather than 'deliver, support, improve'. Not sure how to fix this problem
Think of assembler vs compilers for higher abstraction level languages. When you write in C or Python you trust the compiler to do the right thing and don't routinely review generated assembly let alone machine code.
It's the same here. You write your program in natural language and have the compiler (ai) make it happen. This is what it will converge eventually to.