Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

259

The level of correlation to what was taught to real world give a shit is like 20%. I'm reviewing what was all taught as a job prep / final review of the whole degree and I can not believe how much of it was a waste.

About 80% is just useless made up terminology to go in depth on a subject that DID NOT need to be gone in depth to. Only 20% of the material was real world relevant / give a shitable and the rest of the 80% was term bloat and making a huge class out of over the top effort homeworks to make up effort / work on the term bloat.

Basically 80% of the classes were just teaching you the book, not the topic. The teacher was just a lazy ass and was given a book to teach as a topic so they made a class on teaching the book. Zero relevance on if the book mattered in the real world (likely 20% was directly applicable in the real world, other 80% the made up term bloat).

I can't believe how much time was wasted. And a lot of the classes didn't even matter at all anyways. I've got a cyber security class that spent an entire 3 hour class teaching about the economics behind APARTMENT RENTAL PRICES.

Shit like Software Design. The idea of 'patterns'. Ie 'the singleton'. An object that creates itself on attempting to use it and only allows one instance of itself. That shit is useful. However the usefullness of this info could be taught in a single 3 hour class.

Stuff like 'Algorithms'. Fine that is great. However it's mostly just a brutal weed out class (also fine b/c f off weak coders no offense but they turn into liars in jobs). Teach as many algorithms etc as possible asap.

The level of correlation to what was taught to real world give a shit is like 20%. I'm reviewing what was all taught as a job prep / final review of the whole degree and I can not believe how much of it was a waste. About 80% is just useless made up terminology to go in depth on a subject that DID NOT need to be gone in depth to. Only 20% of the material was real world relevant / give a shitable and the rest of the 80% was term bloat and making a huge class out of over the top effort homeworks to make up effort / work on the term bloat. Basically 80% of the classes were just teaching you the book, not the topic. The teacher was just a lazy ass and was given a book to teach as a topic so they made a class on teaching the book. Zero relevance on if the book mattered in the real world (likely 20% was directly applicable in the real world, other 80% the made up term bloat). I can't believe how much time was wasted. And a lot of the classes didn't even matter at all anyways. I've got a cyber security class that spent an entire 3 hour class teaching about the economics behind APARTMENT RENTAL PRICES. Shit like Software Design. The idea of 'patterns'. Ie 'the singleton'. An object that creates itself on attempting to use it and only allows one instance of itself. That shit is useful. However the usefullness of this info *could be taught in a single 3 hour class*. Stuff like 'Algorithms'. Fine that is great. However it's mostly just a brutal weed out class (also fine b/c f off weak coders no offense but they turn into liars in jobs). Teach as many algorithms etc as possible asap.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (14).
[–] • 1 pt (edited )

Ya I use them sometimes when I want to have a self contained class / "object" like a mysql accessor. It's just for organizational purposes.

Normally I try to keep my programs 90% in object form with other rules such as "objects" are subservient, and only speak when spoken to, and objects do not call or talk to each other. To reduce / eliminate spaghetti code. And 10% follows c style conventions. So maybe a few globals like the command line arguments. Common single task functions under possibly a namespace.

I prefer not to go crazy with capabilities of c++ or the conventions of normal c. Too much OO makes unfollowable and untracable code. Too much c convention is not modularized well or going way out of it's way / bloating to mimic certain things. I prefer to use c++ for it's main purposes, modularizing code, basic polymorphism if you've got a basic abstraction problem or actual similar objects. C otherwise because it's a clean blade of steel.