But anything on your resume or linked from your resume is fair game.

If you haven't been able to meaningfully participate in open-source work there's no penalty, but don't link to an empty GitHub page on your resume.

Nobody is a expert in everything, of course, but if you specifically put "TCP/IP" or "OOP" on your resume, you better be able to explain TCP vs UDP or class vs interface (both real examples from real phone screens I've done).

You could probably drop education from it if you have 5 or more yoe.

Frankly you could do this in one 5 or 6 line paragraph without a resume

I never read them anymore. It’s such a waste of time. Totally useless compared to our phone screen templates.

For example, I might use Chef daily. If I put it in a list of other tools I use it can mean I know how to use it for my very specific use case, but usually it is taken as "this guy thinks he contributes to the Chef source code and knows every bizarre scenario involving it" by some tech screener trying to get his rocks off.

I 100% blame every tech recruiter for furthering this mess.

When I am looking for a job, I send my resume to my curated list of local recruiters followed up by a phone call. We talk about what they have available and what I am looking for. I have enough of a history with them that they make sure that my resume shows up on top of the hiring managers stack.

My success rate from submitting my resume to being invited to an in person interview is 100% unless the req was closed. My non rejection rate is close to 100% (I’ve taken myself out of the running because I found a job.)

Mostly LinkedIn these days. I only got really serious about my career about 10 years ago. Before that I was your typical “dark matter developer” working at one job for almost a decade.

“Hey, I am not looking to make a move right now/I’m looking to make a move in $x months. What are the trends you are currently seeing and what are the salary ranges? Send me a list of open reqs. I might know some people who are looking”.

This will also let me stay up on market trends and know which projects to focus on and what to emphasize on my resume.

I took C and C++ off of my resume years ago even though I did both for 12 years and I still know all of the ends and outs of C. There is going to be that one old geek (I’m 45) who wants to ask me some obscure question just to prove how smart he is. I definitely leave PHP and Perl off. I don’t want to show up on recruiters search results looking for WordPress developers (I never did WP).

I want to keep the conversation and the interview focused.

This is java specific, that's not OOP.

C#: https://docs.microsoft.com/en-us/dotnet/csharp/language-refe... TypeScript: https://www.typescriptlang.org/docs/handbook/interfaces.html

Granted, it might be less prudent to skip some fields than others, of course.

If you have something really notable in your GitHub account, maybe it should probably be on your CV/resume, too!

It feels to me like having a blog site and only putting notes, scraps and drafts in it. Maybe there’s some functionality i’m not seeing?

On the other hand, it's hard to imagine someone senior enough (in terms of experience, not years) who haven't ever hacked a FLOSS dependency to do something it originally didn't.

Of course, it could be that the source wasn't on GitHub, or that author did effort to persuade upstream into accepting their changes and then repository was removed, or that the code is in the company's internal systems (which can be a good idea for various reasons). However, I'd say that most typical scenario is "you see it, you find it on GitHub, you fork it, patch it and leave it there - just in case". I have a bunch of those, and I'm just archiving those repos when I recognize they're not relevant anymore. It's not like I'm paying for those - and having an ancient fork had helped me once, when someone from my old place had a problem and asked me if I still remember how things worked there.

I mean, many (most?) of software engineers are directly working with free software every day. And, sadly, world isn't that perfect this software provides everything one might need without any tinkering. :) So, in a certain sense, "no time for open source" is a little bit questionable.

But, yeah, there are valid reasons why a good engineer may not even have GitHub account at all. Unless you're drowning in a torrent of great-looking resumes (and you're not GitHub Inc.), no harm in not making GH account a mandatory requirement.

No, I find that pretty easy to imagine.

I can think of plenty of developers working in non-OSS (either internal/nonlicensed or proprietary licensed) shops who, even if they have and work with OSS dependencies, and even if they might hack on them for the sake of the projects they work on, have never, by (or at least as a result of the requirements of) employer policy, contributed a thing back.

Of course, that's because I've spent most of my career in that kind of environment, which is why I've got very little on my GitHub none of which has a direct relationship to my paid work.

We work in GitHub, and of those who use their personal profile for work, all of them have "empty" profiles and no meaningful OSS contributions. They spend their free time with their family and in other hobbies.

People who hack on OSS for fun are usually good developers, but good developers rarely hack on OSS for fun especially once they get older.

I meant, using FLOSS libraries for the actual job, during normal work hours. Depends on the industry, of course, I guess.

I think there's many more working on proprietary software, we just naturally don't hear about it due to its nature. Open source is prominent only because it's public.

E.g. I open Slack (a random pick - it's open on my desktop right now), a proprietary software app. And in the "about" section there's a huge list of FLOSS libraries they use: https://slack.com/libs/desktop

Moreover, I'd say, every website out there (and web is a giant niche) uses lots of FLOSS components.

And for GitHub contributions, I meant that once in many years there happens to be a library that's out of date but otherwise useful, or lacks some nice feature.