I wanted to add to your points that I think that there's a lack of understanding in architecture, which the previous generation has learned through refactoring

I wanted to add to your points that I think that there's a lack of understanding in architecture, which the previous generation has learned through refactoring and unit tests. If LLMs will be able to write unit tests, this will get worse, because there will be no time spent reflecting about "what do I need" or "how can this be simplified". These are, in my opinion, how to characterize the differences between a Developer, Engineer, and Architect mindset. And LLMs / vibe coding will never develop actual engineers or architects, because they never can develop that mindset. The easiest programming language to spot those architectural mistakes in is coincidentially the one with the least syntax burden. In Go it's pretty easy to discover these types of issues in reviews because you can check the integrated unit tests, which help a lot in narrowing down the complexities of code branches (and whether or not a branch was reached, for example). In my opinion we need better testing/review methodologies. Fuzz testing, unit testing and integration testing isn't enough. We need some kind of logical inference tests which can prove that code branches are kept and called, and allow to confirm satisfiabilities.