seekayel

It is a good demonstration of how security is a community problem and is limited by the weakest link in the chain.

Are you suggesting with 'Anti-conveyor belt' and 'Reverse QA bottleneck' that the only one testing the code is the person who wrote it? That seems off in my opinion.

Also, does your QA team cycle through the dev side to write tests?

With 6) does that mean squash merge? rebase? otherwise how do you enforce?

Also how do you ensure you deploy something that is tested, vs creating a new version of the code at the time of merge?

Amazing! Do you have any plans to go beyond strawberry picking?

Needs a time suck warning :)

Also, what/how do I use the stickers? Do I give them to other people I am watching fight?

I wonder if anyone has experience with this, or if the take overs are probable?

How I read the article, nothing happened. I think it is a cautionary tale of why you should probably bite the bullet and press the button instead of doing the "easier" thing which ends up being harder and more expensive in the end.

Thanks for wasting 30mins of my day ... haha fun times!

I've opened pull requests that haven't been touched by AWS for ~9 months (comments or other). Been told (through a back channel) that the team didn't have the capacity to review all the PRs.

So "it depends"

Yup (among others). The fact there is such a robust market for additional tooling I think proves that there is a gap in the out of the box tooling for most users.

Haven't used them all. Primarily referring to consistency of interface, visibility of errors and usability of dev tooling (not core product feature).

Any one have experience with using it, either as founder or investor?