Hacker News Reader

Comment by theli0nheart | Hacker News Reader

> Also, the bug buster benefits if they get up high on the leaderboard, because job recruiters will most likely use the leaderboard for lead gen. If you're looking to make a job move, moving up on the leaderboard will help.

I already get plenty of recruiting inbound without having to donate my time to fix bugs for Internet Points.

What you're saying is that this is a worthy use of time for people because they'll maybe move up in the leaderboards which then might lead recruiters to reach out to them.

And after all that, you have to do a phone screen, technical phone interview, a full-day onsite, plus whatever other hoops you'll be made to jump through to change jobs.

Yeah, no. Hard pass. Seems like a huge waste of developers' time.

View on HN

> I already get plenty of recruiting inbound without having to donate my time to fix bugs for Internet Points.

You're not the target audience.

And also, you wouldn't be donating your time. The whole point is that a company puts up a contest for their own employees, who are presumably getting paid to participate.

the target audience are people stupid enough to work for amazon for free. Amazon, fuck you pay me.

So by participating in this, a company is making their own employees more attractive to recruiters?

No the company is getting some extra structure to their bug bash with some prizes provided by Amazon, as well as being able to recruit other people by pointing out how good their current people are (because they are on the leaderboard).

Everything about this seems like a sketch out of The Office (if they were a software company).

Why bug leaderboard is important? Don't I have few ways already to showcase my profile?

1. Stackoverflow to show my expertise

2. Any Open source contribution that shows up in my github profile

How are you employed if you won't fix bugs. These types of devs are so annoying to be around. Crank out weird esoteric hard to read code using every weird meta feature / reflections / introspections they can. Then "hard pass" on fixing bugs as a waste of time.

You do realize most developers are asked to fix bugs anyways, regardless of any silly competition?

Their pitch to Organizations is that

1) They may be able to help you save money 2) They may make it more fun / easier to solve bugs.

Pitch to developers - they'll give you some perks for doing your job.

Note that I also think it's lame because I don't think code guru is that good and don't care about re"invent

Unless I'm completely misunderstanding how this works, this isn't "give you some perks for doing your job." It's getting perks for doing your job, for someone who isn't paying you. And that's what the problem is.

If you want me to fix your bugs, pay me for it. Don't do this gamification nonsense.

Edit: apparently I did misunderstand how this works. It seems like the "Bugbusters" are just a company's normal developers. It still seems kinda dumb, but not as exploitative as I initially thought.

They're marketing page isn't super clear, but it's adding structure for a company's existing bug bashes. You set up a bug hung for your own developers on your own code.

Then why in the world make Internet Widgets, Pty users create yet another login on some random .aws property that (as very best I can tell) does not support any kind of SSO auth that an outside organization would use: GitHub/GitLab, IAM/Cognito nor OIDC/SAML

Yeah, they are just trying to get devs to try their tooling. If tool was amazing, this would be great. But it's hardly the big exploitation people are describing here though it's a bit true that bug fixing is less fun for some and so is often ignored.

That said, other providers of this type of tooling might take some ideas from something like this.

> How are you employed if you won't fix bugs. These types of devs are so annoying to be around. Crank out weird esoteric hard to read code using every weird meta feature / reflections / introspections they can. Then "hard pass" on fixing bugs as a waste of time.

You misread pretty much everything I wrote. My original comment wasn't an explanation for why fixing bugs in general is a "waste of time". My opinion is that uploading your code to this service that uses ML to automatically generate bugs for your team to do a bug bash on is a waste of time.

Our bug backlog has hundreds, if not thousands, of bugs already. We don't need to rely on ML to tell us what to fix.

We have real issues that customers are facing that need immediate attention. This is just a total distraction and a waste of time.

> We will pay you with exposure...

Reply on news.ycombinator.com