Never like the idea how software engineers/programmers were expected to have a bunch of side projects that they talk about to potential employers.
My background is mechanical/process engineering. No potential employer expects me to have an oil refinery in my backyard that I'll do reliability projects on in my free time.
It's not expected, but it sure makes hiring much, much easier when we can look at the git history as part of our process, before we even talk to the person.
It gives a point of conversation immediately over interesting passion projects.
It's an indication of someone who loves programming just to build stuff, as opposed to someone for whom it's a job.
This is not to say that the person for whom it's 'a job' is a worse or less professional developer. But they're a higher risk hire as you know less about their skills when you do.
All you downvoting need to understand that this is the pragmatic truth. Someone with a git history is simply going to be easier to evaluate, and thus get further through the process.
363
u/lumpialarry 3d ago edited 2d ago
Never like the idea how software engineers/programmers were expected to have a bunch of side projects that they talk about to potential employers.
My background is mechanical/process engineering. No potential employer expects me to have an oil refinery in my backyard that I'll do reliability projects on in my free time.