| Yep and yep, but the latter just illustrates the point. On the spectrum of unemployed fry cook to 6-figure tech job, "attracting recruiter spam bots" and "attracting overly-clever recruiters" isn't far from actually Getting There and/or Making It - so long as you keep showing up and making an effort. Definitely not a quick life hack. Long-ish term career moves are really the only reason I check on that stuff anyway, and get more value from the relative rankings of, say, language popularity and jobs, than any number I come to. I work in a job I like, in an industry I like, in a language I like at a very fair rate, so I'm not too concerned about it, but part of that is from figuring out what were dead-ends/non-starters for me, identifying niches, etc. (+1 for the ikigai thing, too). > Nobody cares if you made some 1 line change to some OSS project. Any meaningful change requires more work and effort For sure, if you're presenting yourself as "a [project name here] developer", but the conversation in interviews I've had has tended to center around, say, how we used to use [that horrible old thing] until we found [shiny new thing]. I'm pretty sure I've never impressed anyone with my OSS contributions, save maybe one person who somehow remembered an exact bug and considered fixing it, but I think we were more impressed we both remembered the bug than the handful of lines of code it took to replace `insecureConnections: true` with `insecureConnections: $insecureConnections` and add a `caCerts` property to be passed in to a constructor somewhere. So I guess again, it was the pattern of making minor fixes ("just showing up") rather than being some super l33t hax04 genius or major project maintainer or whatever that got me the credit that mattered. |