I don't see anything on here that I couldn't do with my LinkedIn profile, TBH. I do kinda wish I knew the secrets of how to get 2-3 recruiting emails a day though. Unless it's "have 5 more years of experience," I think my profile could use some help.
The Stack Overflow Developer Story: A New Technical Resume
21–30 of 147 posts
Re: The Stack Overflow Developer Story: A New Technical Resume
#22There is nothing more unreadable than a Stack Overflow resume. Well... except a project on github that doesn't have a readme.
Re: The Stack Overflow Developer Story: A New Technical Resume
#23Earlier quoted context omitted.
I barely even look at SO. It's pretty much like Quora, as far as I'm concerned.
Yes it is like Quora, just with domain specificity. I guess you see this as a bad thing, but both sites are tremendous fonts of information. What is preferable to you? Academic papers? Books? Conference Talks? Random Blog Posts? Man pages?
Stack Overflow is certainly better. Probably 90% of the time you can dig up the correct answer somewhere on the page.
But it's incredible how much of the world's knowledge is still locked away in books. The internet is ok for computer programmers, but for basically everything else it feels like we're still decades away from the "information superhighway" dream.
Re: The Stack Overflow Developer Story: A New Technical Resume
#24Wait so hiring managers who didn't have more then 60 seconds to parse my resume now have the time to go through years of my stackoverflow activity? Sweet!
Re: The Stack Overflow Developer Story: A New Technical Resume
#25Re: The Stack Overflow Developer Story: A New Technical Resume
#26Re: The Stack Overflow Developer Story: A New Technical Resume
#27The traditional resume works because it's easy to scan visually quickly. It's easy to print out and share. This is not.
Re: The Stack Overflow Developer Story: A New Technical Resume
#28Weren't GitHub profiles the new technical resume? How well did that work in practice, and how would this Stack Overflow approach be different? I was under the impression (from reading HN/Reddit) that while engineers do read GitHub profiles if explicitly linked in a resume, nontechnical recruiters do not. And they are the gatekeeper to said engineers.
Re: The Stack Overflow Developer Story: A New Technical Resume
#29He squeezes in a humblebrag: "...if you're like me, and still just a little proud that you got off the waitlist and eked your way into a school above your intellectual weight class..."
And he uses scarcity to scare devs into creating a profile: "It only takes a few minutes, and you do NOT want some other joker snapping up the good URLs."
Re: The Stack Overflow Developer Story: A New Technical Resume
#30Resumes in their current form don't work well as a source of truth about anyone's career. The main issue being that we put summarized/editorialized information in instead of details. It's like discarding the data you used to generate a chart and then updating the chart directly going forward.