Upper, also, nice boobies.

The problem you describe doesn't seem to be caused by Agile but a symptom of poor architecture. In general, I'm opposed to monolithic applications and prefer a micro services approach.

You make some good points but you are kind of throwing the baby out with the bath water. No one style of programming is suited to every project. Also the inheritance diamond problem you used in your opening paragraph is a solved problem in OOP that has been discussed ad nauseum. You must have heard the phrase "composition over inheritance". Wikipedia has a good explanation if you are unclear.

You've been doing JavaScript so long that it has rotted your brain. What you describe is merely a less organized way of doing something resembling classes.

The bigger your application gets and the bigger the team that works on it, the more important organization becomes. There are great frameworks written in js that can help you stay organized, but js is not really superior to other languages.

It's really easy to make a big mess with it because it doesn't enforce much of anything. That's great for writing quick and dirty scripts, but when you work on a large app you need to be more careful than in other languages.

This is incorrect, misleading info. u/qwop gave an accurate description of the void return type in C++

Not "whatever", it means "nothing", "nothing, Lebowski!" "Vee are nihilists!"

How much you want to bet he was forced to retract that paper because his school was like "hey we can't go around telling kids that most of them will never learn to program, how will we make any money? You retract that or you will be fired and blackballed!" Lol

I've interviewed hundreds of candidates for programming positions and it is most certainly not BS. Programming is more than a learned skill, it is an aptitude. Not that many people are capable of ever learning how to program. Their brains just don't think that way. Congrats, you are a programmer, as this test is easy for anyone who has the aptitude.

Rolls eyes... There is no right way for everything. Every different solution to a problem comes with its own pluses and minuses. Weighing those against alternate solutions will point you to the right way to handle the task at hand. OOP is great for some things, functional for some things and procedural for smaller applications perhaps.

Procedural code is not typically reusable though. But if you have a small, one off task, it will be the fastest to get done. Those small one off things have a nasty habit of becoming bigger beasts though. YAGNI still applies I suppose.