87
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Dec 2023
87 points (98.9% liked)
Asklemmy
43394 readers
1126 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
Like... Literally any of it. I'm a software engineer and my degree didn't have anything to do with software or engineering.
I'd have to really stretch to something like "time management" or "active listening" to find any connection, lol.
Computer Science was great dont get me wrong, but I totally agree. Comp Sci helped with some of the basics, but didnt prepare you at all on the soft skills that get you ahead, nor why task management, version control, and other such concepts are so important.
I can't believe in my comp sci course they never went over git. Like cmon that's core to software development these days.
It's a little unfair to criticise a CS course for not being a SWE course. But I agree that graduating students in CS without having covered the basic requirements in the SWE day job most of them will move into is a disservice.
I did CS (30 years ago) and things entirely missing in the syllabus back then: