What I learned from spending 3 months applying to jobs after a coding bootcamp

Re:What I learned from spending 3 months applying to jobs af... by throwawaysbdif on Tuesday November 22, 2016 @02:32PM (#13016823)

Because I can explain anything about it. because the module is published on maven central under my name with my private key, hosted on a domain registered to me, on a GitHub account that's literally my name and a domain that's my last name. My primary email is [email protected]. A common theme with employers not checking GitHub is that the code could be lifted but in some cases it's glaringly obvious that it is not.

I mean what if I'm applying for jobs using someone else's resume? What's stopping me from having my coder buddy do the phone screen for me? Why don't I just list a bunch of experience at companies that went under... Unverifiable. Use a bunch of references that are actually my roommate and my dad with Google voice numbers.

At a certain point you just have to take things at face value. A GitHub is just as verifiable as every part of your resume that's not a school you went to or your identity

[ Parent | on HN ]

Re:What I learned from spending 3 months applying to jobs af... by garysieling on Sunday November 27, 2016 @03:37PM (#13051371)

That's fair. I don't think I've really seen readmes on the github projects people list on their resumes, let alone seeing their stuff published to maven.

I do think the original article suggests that if employers put a lot of stock in github, the coding academy people would quickly have the "best" github pages.

[ Parent | on HN ]