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

©2025 Poal.co

710

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)

[–] [deleted] • 3 pts

A singleton is just a way to have a global variable without admitting that there's literally nothing wrong with global variables.

Change my mind.

[–] • 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.

[–] [deleted] • 0 pt (edited )

A global variable can be accessed by anything a singleton can only be accessed by something its injected into and can also have state update logic built into it.

[–] • 2 pts

I recall having 3 weeks of some very weak SQL. Other than the cobol and osi introduction, not much learned of real world value.

[–] • 1 pt

I'd go so far to say even the OSI model is kinda useless. I mean conceptually ok, but when I'm troubleshooting a problem I'm not thinking "oh it's a level 3 network problem!" I'm thinking "fucking idiots plugged in a loop."

[–] • 1 pt

Agreed, it is esoteric but it explains at a high level how things should relate. The class period that it is taught is enough.

[–] • 1 pt

I've had two different interviews that wanted me to rattle off the OSI layers like my ABCs. The second time I told them it was a waste of time as it would never come up in day to day operations. I did not get either of those jobs.

[–] [deleted] • 1 pt

yeah, I had one whole semester on the history of computer science...

[–] • 0 pt

Computer Science is not a trade school for writing software. It’s like getting a degree in mechanical engineering and saying it’s not useful for your job as a dealership mechanic.

If you thought Algorithms was a waste then you definitely should not have ever enrolled in a CS curriculum.

[–] • 1 pt

That’s true, and yet most common developer jobs want a CS degree. It doesn’t matter that you won’t be implementing your own database management system, or your own compiler, the CS degree is the gold standard no matter how irrelevant most of it is.

[–] • 1 pt

All but 3 classes were incredibly inefficient. OS and Algorithms were pretty much the only two classes to the brim were good content filled classes. The only problem with those is why were they completely retaught as a masters class? These are already given as undergrad.

Most the rest had a lot of good content but the class only needed to be 20-30% of it's original self to get the actual content taught.

Ie a databasing class. I learned and incredible amount of how to design your tables and how to setup pure god like sql calls. And how to make those calls return in like 1s or less over 1gb of data. And some more overall info on db systems however the whole class could have been 50% the amount of classes or less to get that same important information.

[–] [deleted] • 0 pt

Computer Science is a trade school for being a Computer Science teacher.

[–] • 0 pt

Yeah, If op doesn't think that patterns and algorithms are useful, I wonder what is useful?

Will architected software and systems will depend upon patterns and algorithms.