

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!
I think it can be both. However they are no justification as to why one should buy and like a game they clearly won’t like for various reasons. Even more, trying to “fix” a game can alter the game’s impact on the player. There’s a reason why roguelikes/roguelites are so hard, and taking away the difficulty will lessen the experience. That’s why most people also, for example, won’t use cheating tools for their single player games apart from screwing around.