Live data from Hacker News

AWS BugBust

aws.amazon.com

51–60 of 100 posts

Re: AWS BugBust

#51
Given how amazon has eroded trust with things like Sidewalk, why would I give them free time to improve CodeGuru and fix bugs?

Amazon has been openly adversarial to businesses, including software companies, so what goodwill are they banking on?

Re: AWS BugBust

#52
post #47
post #38

Earlier quoted context omitted.

The companies that put up the contest benefits. For a lot of people at a lot of companies, a trip to re:invent is a huge prize. If your job is to fix bugs anyway, now your company just incentivized you to do it more and in your off time to win that prize. 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…

> The companies that put up the contest benefits > if you’re looking to make a job move,… Why would companies allow their best developers to be poached? Unless of course there’s a way for companies to keep their developer scores private…

The risk to the company is pretty low that their employee would show up on a global leaderboard. And even if they do, they can give them a raise or other benefits. It helps them determine the market rate for their employee.

Re: AWS BugBust

#53
post #13

When I read the announcement, I thought they were donating the use of CodeGuru to projects (which I presumed would be limited to open source ones) to (1) improve the code hygiene of the world (2) gather more data for their machine learning models (3) publicity for CodeGuru But as best I can tell, this is the worst of all worlds: I have to already have an AWS account to both create the competition and also to point Co…

Quite frankly I've never seen people use AWS offerings for CI pipelines, I wonder if other products (Code* family) are any good - can anyone comment on them? I've only used CodeCommit once during a hackathon, and it seemed rather basic.

I have used CodeDeploy/Codepipeline/Codebuild over several years. Overall they work well but there can be edge cases or gotchas that show up on occasion depending what you are trying to do.

I also prefer externalizing the CI/CD process with Jenkins or Spinnaker-based setups.

Re: AWS BugBust

#54
post #6

I'm struggling to find a compelling reason why someone would participate in this? Looking at https://aws.amazon.com/bugbust/ the prizes are yet more corporate trash that don't need to exist ("AWS BugBust Varsity Jacket" okay ), and they have a pricing page so it's not even free. All this tells me is that Amazon doesn't value your time

Reminds me of a former Atlassian-based t-shirt reward for setting up the entire suite of Atlassian products (here be dragons or some logo like that). Glad to see there are many others who value their time and are not content to be treated like children in exchange for their time and effort.

Re: AWS BugBust

#55
post #13

When I read the announcement, I thought they were donating the use of CodeGuru to projects (which I presumed would be limited to open source ones) to (1) improve the code hygiene of the world (2) gather more data for their machine learning models (3) publicity for CodeGuru But as best I can tell, this is the worst of all worlds: I have to already have an AWS account to both create the competition and also to point Co…

Quite frankly I've never seen people use AWS offerings for CI pipelines, I wonder if other products (Code* family) are any good - can anyone comment on them? I've only used CodeCommit once during a hackathon, and it seemed rather basic.

I'm going to chime in and say the only benefit we got from CodeDeploy was its cost was folded into our AWS account. We didn't have to go through the hassle of explaining why we need "yet another I appreciate this is a bad reason to recommend a service, and am not defending it. Just explaining why we wound up using it.

The service itself is not horrible, but like every other AWS service, I felt like I was definitely not in the target market: some easily implemented feature was left out and the configuration space easily allowed you to specify things that weren't covered in the (very) thin documentation and seemed to behave unexpectedly.

Re: AWS BugBust

#56
post #52
post #47

Earlier quoted context omitted.

> The companies that put up the contest benefits > if you’re looking to make a job move,… Why would companies allow their best developers to be poached? Unless of course there’s a way for companies to keep their developer scores private…

The risk to the company is pretty low that their employee would show up on a global leaderboard. And even if they do, they can give them a raise or other benefits. It helps them determine the market rate for their employee.

> The risk to the company is pretty low that their employee would show up on a global leaderboard.

This invalidates your other point that it benefits developers. Why would a dev sink countless hours for a “very low” chance at being on the global leaderboard and hence moving jobs.

You can’t simultaneously posit it’s good for both companies and developers.

Re: AWS BugBust

#57
post #56
post #52

Earlier quoted context omitted.

The risk to the company is pretty low that their employee would show up on a global leaderboard. And even if they do, they can give them a raise or other benefits. It helps them determine the market rate for their employee.

> The risk to the company is pretty low that their employee would show up on a global leaderboard. This invalidates your other point that it benefits developers. Why would a dev sink countless hours for a “very low” chance at being on the global leaderboard and hence moving jobs. You can’t simultaneously posit it’s good for both companies and developers.

> This invalidates your other point that it benefits developers.

Not at all. The company undervalues their employee and sees little risk in them showing up on the board, and the employee overvalues their skill, thinking that showing up on the leaderboard is a shoo-in. Maybe the employer is right, maybe the employee is right, or maybe both or neither is right.

Also, the employee does it because they get paid to hunt bugs regardless. It just helps the company by putting a structure around what they are already doing.

Re: AWS BugBust

#58
post #27

Earlier quoted context omitted.

The $769 is referring to the estimated money saved by fixing bugs, rather than the trade in value of the points. > For information on how points are awarded, see the Official Rules. Actual savings may vary. Section 5 of the official rules document states approximate retail value of the prizes as; reInvent:$4000, Resin Trophy:$60, Hooded Sweatshirt:$27, tshirt:$12 https://d1.awsstatic.com/product-marketing/bugbust/AWS…

That's exactly my point - Amazon have given that figure as their estimated savings, so either that's an insanely overinflated figure, or my point stands and if you save one of their clients several tens of thousands of dollars they'll give you a "prize" of a tshirt. They probably spent more money producing that video than they will pay for all the t-shirts they'll give out. $77,000 for a t-shirt. $1,500,000 for a jac…

I think you misunderstand, you fix your own code not somebody else's. The BugBust is basically them advertising trying out their new CodeGuru analysis tools for free and sending some prizes to the ones that use it the most.

Re: AWS BugBust

#59

Earlier quoted context omitted.

Quite frankly I've never seen people use AWS offerings for CI pipelines, I wonder if other products (Code* family) are any good - can anyone comment on them? I've only used CodeCommit once during a hackathon, and it seemed rather basic.

I'm going to chime in and say the only benefit we got from CodeDeploy was its cost was folded into our AWS account. We didn't have to go through the hassle of explaining why we need "yet another I appreciate this is a bad reason to recommend a service, and am not defending it. Just explaining why we wound up using it. The service itself is not horrible, but like every other AWS service, I felt like I was definitely n…

Many SaaS companies offer the ability to pay for themselves via the AWS marketplace so you can have everything under one EDP / bill (though AWS takes a little cut in this case).

Re: AWS BugBust

#60
post #38

Earlier quoted context omitted.

The companies that put up the contest benefits. For a lot of people at a lot of companies, a trip to re:invent is a huge prize. If your job is to fix bugs anyway, now your company just incentivized you to do it more and in your off time to win that prize. 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…

> 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 mayb…

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

Post reply on HN