Live data from Hacker News

AWS BugBust

aws.amazon.com

11–20 of 100 posts

Re: AWS BugBust

#11

Has anyone had a positive experience with Code Guru? All I've seen so far is that it's _very_ expensive, and provides the sort of feedback I expect from open-source linters and static-analyzers, and without any understanding of how appropriate those recommendations might be in context. I've only really seen it for Python though, maybe it's better for other languages?

Better to start with defining the problem that you are solving and whether or not you need to solve it before even delving into that particular rabbit hole. ROI on analysis is usually fairly low unless you’re in a regulated industry or the product is cheap or free.

Re: AWS BugBust

#12

Has anyone had a positive experience with Code Guru? All I've seen so far is that it's _very_ expensive, and provides the sort of feedback I expect from open-source linters and static-analyzers, and without any understanding of how appropriate those recommendations might be in context. I've only really seen it for Python though, maybe it's better for other languages?

The profiler is very good as part of your CI automation, you can alert on regressions and such.

Re: AWS BugBust

#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 CodeGuru at the repos, then I have to pay for running CodeGuru on any potential PRs, but then also separately create a BugSnag account seemingly just for this stunt. And in the end I ... get Internet points on my BugSnag account?

I fail to see how anyone but AWS benefits from this, unless a participant happens to be one of the top competitors who accumulated enough Internet points to get a free trip to re:Invent

Re: AWS BugBust

#14
post #10

For those who are wondering the rewards aren’t worth it… this is not Amazon asking for oss contribution to their AWS source code. This is for private companies to offer bug fest to their own employees / target audience. > customers can set up private AWS BugBust virtual events Why should the jacket be sponsored by Amazon? I don’t get it.

Why would they need AWS to do so? Engineers in companies don't know every line of code in their product - many of them are siloed in their own teams.

A team can easily just dedicate an hour or two a week and do their own bug bash, right?

Re: AWS BugBust

#15

kind of cool how they just "Created" a market place out of nowhere with their huge aws offerings. I can see this as a future repository challenging stack overflow, and with automation, challenging other CI pipelines, and then as someone else mentioned these magic carrots could be used as hackerrank/linkedin/hiring.

That's only true if people start to use it, which for sure isn't a given with the current incentives. Also, there is 100% no way this challenges S.O. in any way

Re: AWS BugBust

#16
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

>the prizes are yet more corporate trash that don't need to exist

What I can't wrap my head around is that the top of the FAQ says that 1 Point has an estimated Dollar Equivalent of $769, and for 100 Points you get a t-shirt. As a "prize" in exchange for saving $76,900 I'd be expecting a car at the low-end...

Re: AWS BugBust

#18

Has anyone had a positive experience with Code Guru? All I've seen so far is that it's _very_ expensive, and provides the sort of feedback I expect from open-source linters and static-analyzers, and without any understanding of how appropriate those recommendations might be in context. I've only really seen it for Python though, maybe it's better for other languages?

We had similar experience! We tried CodeGuru Reviewer on one of our Python codebases (around 71 KLOC) and abandoned it after a week.

The feedback was indeed similar to what standard linters and static analyzers can provide with more noise. I have no doubt they can improve their recommendations as they get more feedback and analyze more codebases, but we were not interested to pay to contribute.

We have had much more success with https://deepsource.io/ , which found real bugs and we generally agree with their recommendations. We are currently evaluating whether or not we will include this service as part of our process.

Deepsource is rule-based, but my understanding is that they are starting to use ML to rank recommendations.

Re: AWS BugBust

#19
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

> they have a pricing page so it's not even free

BugBust itself is free. You pay for usage as per normal for CodeGuru Reviewer and CodeGuru Profiler (after the 30 day free trial of BugBust and 90 day free trial of Profiler).

Re: AWS BugBust

#20
post #10

For those who are wondering the rewards aren’t worth it… this is not Amazon asking for oss contribution to their AWS source code. This is for private companies to offer bug fest to their own employees / target audience. > customers can set up private AWS BugBust virtual events Why should the jacket be sponsored by Amazon? I don’t get it.

Why would they need AWS to do so? Engineers in companies don't know every line of code in their product - many of them are siloed in their own teams. A team can easily just dedicate an hour or two a week and do their own bug bash, right?

This pairs it with the AWS bug finding AI tools to automate the bug bash overhead. I.E. Finding bugs, assigning point values, keeping track of point values, etc.
Post reply on HN