this post was submitted on 20 Jul 2023
386 points (95.5% liked)

Programming

16975 readers
1288 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
 

Initially, LinkedIn was just another site where you could find jobs. It was simple to use, simple to connect with others; it even had some friendly groups with meaningful discussions.

And then it gained monopoly as the "sole" professional network where you could actually land a job. If you are not on LinkedIn now, you are quite invisible in the job market. Recruiters are concentrated there, even if they have to pay extremely high prices for premium accounts. The site is horrible now: a social network in disguise, toxic and boring influencers, and a lot of noise and bloated interface to explore.

When Google decided to close their code.google.com, GitHub filled a void. It was a simple site powered by git (not by svn or CVS), and most of the major open-source projects migrated there. The interface was simple, and everything was perfect. And then something changed.

GitHub UI started to bloat, all kinds of "features" nobody asked for were implemented, and then the site became a SaaS. Now Microsoft hosts the bulk of open-source projects the world has to offer. GitHub has become a monopoly. If you don't keep your code there, chances are people won't notice your side projects. This bothers me.

Rant over. I hate internet monopolies.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago (2 children)

What they're asking for is a public portfolio.

Obviously, you can't give them code that legally belongs to a past employer and they're not allowed to look to avoid accusations of copyright infringement.

Especially if they do any reverse-engineering for interoperability, there must be zero suspicion that they were inspired by code they're not allowed to use.

This is where open source contributions under permissive licenses come in.

Something shown to work in a real project is also viewed better than out of context code snippets.

When you're essentially saying you have nothing to show them, you're indistinguishable from someone who actually has nothing and is lying about their skills, so the onus is on the interviewers to vet you, which for various reasons may not be possible, so they'd rather just move on to someone with a clearly proven track record.

[–] [email protected] 3 points 1 year ago

Ok but the original point still stands. Coding outside of work and at work is poor work life balance. Even my own projects I do are to learn not solve an actual problem in the world with code.

[–] [email protected] 1 points 1 year ago

And a public portfolio is the CV that states "I worked for this company making thier products". They might ask for the specific products, but there's a chance some people never made public ones.

Github is for college and thesis projects. That's what most people have on there.

The correct answer to these recruiters is still not stated yet. When they say

"Your github is empty"

People should answer

"I only produce code that actually makes money".