this post was submitted on 19 Jul 2023
1095 points (98.3% liked)
Programmer Humor
32733 readers
544 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So it really is like that eh?
Do you have any tips for what could help me, even a little bit, to have better chances?
Build an open source portfolio. Being able to show employers what I was capable of was a massive benefit both then and now. You can say you know all of these things, but when you're looking at hundreds of applications one of the first things they do to reduce the pile is filter out people who don't have some kind of online presence like Github. This allows them to see that you're actively engaged with the field and if they want to interview you, to look at your code quality and experience.
A personal website that highlights your best work is also a good idea, as it helps to even further distill down the things you're ultimately going to end up talking about in an interview. It doesn't need to be anything fancy, just something that shows your competent. I wouldn't expect the person interviewing you to actually hit view source and criticize your choice in frontend framework.
Without any prior professional experience, is an extensive open-source/[other non-professional software development related experience] portfolio perceived as more valuable than a degree to employers?
That entirely depends on the employer, but in my anecdotal experience that has been the case. Especially in more recent years versus the start of my career (nearly 20 years ago).
The reality is that Computer Science is useful for building strong engineers over the long-term, but it doesn't at all prepare you for the reality of working in a team environment and contributing code to a living project. They don't even teach you git as far as I'm aware.
Contributing to open source demonstrates a lot of the real-world skills that are required in a workplace, beyond just having the comprehension and skill in the language/tool of choice you're interviewing for.
Yeah, I do that actually, though I keep a "serious" profile where there's little activity and another one where I can just do whatever so I engage a lot more with other projects and make some experiments for myself, so it also ends up being the most active, but I don't show it, maybe I should?
In my experience interviewers look very pleased when I show them what I made, but they don't seem to dig into it much most of the time, so I don't know how important they really find it.
I'll definitely try to put more emphasis on those anyway, so they can see a good showcase.
That sounds interesting, I'll definitely try that, thanks!
Yeah, I do that actually, though I keep a "serious" profile where there's little activity and another one where I can just do whatever so I engage a lot more with other projects and make some experiments for myself, so it also ends up being the most active, but I don't show it, maybe I should?
In my experience interviewers look very pleased when I show them what I made, but they don't seem to dig into it much most of the time, so I don't know how important they really find it.
I'll definitely try to put more emphasis on those anyway, so they can see a good showcase.
That sounds interesting, I'll definitely try that, thanks!
Yeah, I do that actually, though I keep a "serious" profile where there's little activity and another one where I can just do whatever so I engage a lot more with other projects and make some experiments for myself, so it also ends up being the most active, but I don't show it, maybe I should?
In my experience interviewers look very pleased when I show them what I made, but they don't seem to dig into it much most of the time, so I don't know how important they really find it.
I'll definitely try to put more emphasis on those anyway, so they can see a good showcase.
That sounds interesting, I'll definitely try that, thanks!
Just a heads up, you replied multiple times to this. If the client you're using doesn't submit immediately, that just means it's not doing error handling properly and not disabling submit buttons while the request is in flight. You've actually submitted once for each time you pressed the button
Omg haha, sorry about that! I believe the server was having problems just at that moment, since I couldn't access lemmy.world anymore, I guess they ended up being sent through after the outage (was I the only one experiencing it?)
Looks like it wasn't just you, a bunch of large instances just had an outage
Yeah, I do that actually, though I keep a "serious" profile where there's little activity and another one where I can just do whatever so I engage a lot more with other projects and make some experiments for myself, so it also ends up being the most active, but I don't show it, maybe I should?
In my experience interviewers look very pleased when I show them what I made, but they don't seem to dig into it much most of the time, so I don't know how important they really find it.
I'll definitely try to put more emphasis on those anyway, so they can see a good showcase.
That sounds interesting, I'll definitely try that, thanks!