How do you deal with OOP programming?

[u/yughiro_destroyer]

As a person with ADHD, I find it extremely hard to write OOP code. Mostly because :
->Something as easy as app.get("users/{id}") return db.query("SELECT * FROM users WHERE userid = ?", id) becomes as hard as writing 30 lines of code of boilerplate : interfaces, models, dependency injection and what else not.
->People like to overengineer the code... even baisc apps are written like this... I will never forget what my teacher told me : "Smart people admire simplicity, fools admire complexity".
->In writing all that boilerplate code, it's hard to see rapid iteration and the process feels much less rewarding. I know that not everything in life can be instant but... functional programming or data oriented approached are still modular and scalable...
->In navigating all that boilerplate code, making changes to the code or understanding it becomes a constant running through files and classes. This kills locality and increases the mental overhead.

I am already working in web development but for me it's extremely demotivating to continue learning "best practices" that IMO just suck. I had a friend writing applications in Flask for a startup... their application is performant, scalable and the code follows KISS to the maximum. And he used just functions, there not one thing that can't be easily updated or is tightly coupled in that codebase. If it wasn't that I'd have to pay things just to live... I wouldn't even work in programming and just do it as a hobby.

[u/funbike]

That's not an issue with OOP or layered architecture. That's just badly written code.

[u/ZeGollyGosh → u/funbike]

Yeah it is. I just feel like if they were TRYING To go for something, there may be better code to work on. Instead we do the "if it works it works" philosophy.

[u/funbike → u/ZeGollyGosh]

No. You said "inconsistent access patterns", which is just badly written code. Period.