We need AI hype off of this platform. LLMs and such are only important for science. Everything else is just massive waste of resources which we absolutely dont have and cant spare as a population. We need 100% renewables NOW and we need to stop expanding AI immediately.

This will just lead to more low-quality code.

I instead recommend using more productive languages. I’ve heard many good things about Rust, if you can deal with the OCaml-like syntax and the functional paradigm by default. As an alternative I can also recommend D, it doesn’t have the “const by default” issue of Rust (functional paradigm is still possible, you just have to opt-in), a very C-like syntax except more refined, memory safety features (3 levels of memory safety + arrays with bounds checking), at the cost of a bit hard to opt-out garbage collector (you also have to opt-out from many D features and the already scarce library ecosystem).

Honestly, I think that this was a horrid read. It felt so unfocused, shallow and at times contradictory.

For example, at the top it talked about how software implementation has the highest adoption rate while code review/acceptance has the lowest, yet it never really talks about why that is apart from some shallow arguments (which I will come back later), or how to integrate AI more there.

And it never reached any depth, as any topic only gets grazed shortly before moving to the next, to the point where the pitfalls of overuse of AI (tech debt, security issues, etc.) are mentioned, twice, with no apparent acknowledgement of its former mention, and never mentioned how these issues get created nor show any examples.

And what I think is the funniest contradiction is that from the start, including the title, the article pushes for speed, yet near the end of the article, it discourages this thinking, saying that pushing dev teams for faster development will lead to corner cutting, and that for a better AI adoption one shouldn’t focus on development speed. Make up your damn mind before writing the article!