Would be interested in an article about stopping OOP. I see myself often drifting towards classes and abstractions once my code grows in complexity

This is the video that's been going around. It's a bit long and could have been compacted into a 20 minute video, but if you have the time, it's a good overview for people without a computer science background.

"Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025" https://youtu.be/wo84LFzx5nI

But if your point is there aren't any written articles about stuff like this, I agree. If they're out there, they're a bit outside the mainstream.

You go into work and discover that a coworker isn't happy with some code you wrote because they don't like it. They go to your manager and tell them that you're being a problem by writing code they don't like. Your manager, being very skilled in conflict resolution, makes a technical decision to avoid whatever tool you used which caused the problem. In your case it was OOP.

That's it. You've been told. No more OOP.

The manager has figured out what's good for the business and you figure that listening is what's good for your job.

google richard feldman (roc lang creator) talk about using just functions and data.

don't remember exact title, sorry, but description i used above is close, iirc.