I agree, but is this really something that needs to be a blog post? You could have easily commented it on the HN post or sent the author an email. This brings to mind the recent discussions of negativity on HN.

Glad to see this got some discussion. Someone else commented on the blog post suggesting I open a pull request, correclty pointing out it would have taken the same amount of time as writing the post. I'll paste my response to them below to clarify why I chose the route I did-

Well aware [I could have opened a pull request] thanks Carina. I took a gamble that this would be a more effective route after opening an issue here https://github.com/resume/resu... and noticing 19 others open, many around 2 years old with code attached and no response. Not sure if you've had a very different experience but I'm pretty cognizant of those factors when choosing who to bother submitting code to at this stage.

I actually did spend a little time putting breakpoints in Chrome before posting, but based on circumstances felt that my best chance to get it addressed was to shed light on the underlying issue in a way that might get a volume of other folks involved.

I think it's a great suggestion, but TBH if your seven-figure hiring manager is making a snap decision based on a username and a single tool when she could look at your Github profile directly, I doubt the Github Resumé software is the "weakest link" in this decision-making process.

Even better than making this blog post would have been to make a pull request to the public repo that runs the site (https://github.com/resume/resume.github.com). It's written in JavaScript. Seeing as you're (http://resume.github.com/?beezee) not only an experienced github user but also an experience javascripter, I would guess that it's well within your capabilities.

See a problem in the world? Fix it. Especially when it's trivial based on your skill set!

Well you could have just posted this as a comment in the previous discussion. However, it does bring up the good question of how do you pass the blame around when something doesn't look right? You dont! No matter how many times you tested your algorithm, never assume it will catch a culprit with 100% accuracy and please don't make a program to accuse someone of something. It is embarrassing when you have a false positive and you accuse your paid customers of piracy or when a potential investor gets his email auto-returned accusing him of being a spammer.

I think you're over-reacting a bit. Github Resume isn't an official Github service. Some guys created the account "resume" and are using that to generate resumes: https://github.com/resume

So, while the critique is certainly valid and this needs to be addressed, so I think "I never asked to have a github resume, and I can’t opt out" is a bit of a hyperbole (because Github isn't putting a "resume" button next to your account!)

You should probably have raised an issue or debugged this; TBH I think this post is doing you more damage. Rather than fixing something, you moaned about it.

If you can't opt-out and a service "blames you" for something that went wrong, i think it deserves a little more than "a comment".