Asklemmy

I can't believe in my comp sci course they never went over git. Like cmon that's core to software development these days.

My university created an entirely new school because while the computer science graduates could do computer science they couldn't write an email or contribute to a meeting.

Heh yeah. Lots of fresh grads don't even really know anything about application development. Like they have a handful of sorting algorithms memorised and can explain what a compiler does (and are thinking about writing one some day) but can't actually build anything.

Often, they can pick it up quickly, whatever the "it" is... But it doesn't give them that much of a head start compared to someone who did a shorter program or self-taught.

I've never used PuTTY either, tbh... Is that just what Windows users use for SSH stuff?

You just apply anyway.

Usually they’re not willing to pay anywhere close to doctorate money for doctorates anyway, and will end up settling no matter who they pick.

I’m not sure if i’ve ever known any engineer who has met the listed job requirements for their role. They say requirements, but what they mean is “this is my ideal”. Put another way: think of it like a dating app profile. dude may act like he only dates 10s in his profile, but you show him some attention and suddenly you’re just as good as a 10, because he’s lonely and needs affection from someone.

Basically, for most companies, they’re essentially the corporate version of incels. Way too high of standards, but will settle for anyone who is into them regardless of what they think their standards are, because they just need someone ASAP, and their standards disappear quickly once you make yourself available.

I’ve enjoyed a 20+ year long career as a programmer, and I dropped out of college 3 months in because i couldn’t afford it. That’s because early in my career i took a few shitty jobs until i had a decent enough resume that i didn’t have to take shitty jobs anymore. That took study and practice and passion in programming, but i did that for fun years before i even showed up on the university doorstep.

I dunno, most of the job descriptions I see say something like "a relevant degree or equivalent experience..." And lots of places don't even list an educational requirement, at least for more senior roles.

I basically self-taught while I was working in a different field, and then eventually found a bootcamp with a good alumni network and career placement services. Once you get a little bit of experience, it starts to snowball, but getting that first opportunity (or first few) can be a steep hill to climb.

Oh, and you gotta be pretty good at building software too, of course, but not as good as you'd think to get going-- Most of your learning is on the job, regardless of what educational path you take. In that respect, most go-getters with some diligence and aptitude can exceed the capabilities of a typical compsci grad inside of a year, I'd say.

There will always be employers who think the degree is really important, and there will be roles where it actually is... But plenty just want evidence that you can do the job well.