I guess the idea is AI gives you back time so you could now do the 20% but you still really can't because you have to still think about it even if the code is generated? Not even sure after reading all that text what the idea is .

It is definitely factual that there is a complete paradigm shift in the prioritization of quality in software. It's beyond just AI side effects, and now its own stand alone thing.

There have always been many industries, companies, and products who are low on quality scale but so cheap that it makes good business sense, both for the producer and the consumer.

Definitely many companies are explicitly chosing this business strategy. Definitely also many companies that don't actually realize they are implicitly doing this.

Wether the market will accept the new software quality paradigm or not remains an open question.

It's not a technical issue, it's a 'software doesn't really kill people so government doesn't intervene in it'. In the case where the software is life and death it's generally developed in ways similar to 'real' engineering

Fundamentally folks built building/structures without engineering, just so consistently caused death and destruction that govt stepped in and started requiring licensed trained folks, approval trails etc. without this real world intervention regular physical 'engineering' the same crap shoot as software engineering.

This isn't syntax vs abstraction. This is how much programming language power do you want to enable in your configuration language. This is a big difference and I think we miss the interesting part of that discussion because we dip into this 'abstraction angle.

After fully reading the article I came to understand it really was not referring to anything sqllite specific, was really 'what if you ran postgres as an application on a server', there really is nothing more to be gained from reading the article beyond this, and this is kind of the most basic deployment model for postgres for like the last 40 years.

Imperative programming style has many advantages over functional for some problems. Functional programming style has many advantages over imperative for some problems.

The only clearly 'wrong' approach is codebases where you can look at the code and determine a specific developer on the team wrote feature x because it fundamentally looks completely different from the other sections.

Just for clarity: - Non-Japan Asia is new to gaming, and that's okay, it's going to take some time before they find their own voice.

This is not factually true, video games have one of the most popular forms of entertainment in non Japan Asia for 25 years. Nearly a quarter of humanity lives in non-japan asia. There were good non japanese games, bad non japanese games, and more than anything tons of 'mid' non japanese games. They aren't new too it, and they do have their own voices and styles.

What gets talked about as history of video gaming tends to reflect American video gaming history and the unavoidable influence of America's number one vassal state, Japan. Really this is the history of games marketed in North America and that's fine, it just isn't the whole history.

A more useful article would actually walk through the cost/complexity trade

It doesn’t make sense to clean everything to a perfect condition but there should be some amount of ‘keep your room clean’ level of hygiene that’s maintained

It’s a fake industry held up by VC money.