A fair share
How much money a developer saved by spotting the issue? Millions?
This will probably not change the "market rate" (a code word companies use to fix the market) salary of theirs.
Cassandra 4.0 – the open-source distributed NoSQL database used by Apple, Netflix, and Spotify – has been delayed at the 11th hour after a developer spotted a bug in the code. Project contributors had committed to making the much-anticipated release the most stable yet and wanted to ensure it shipped with no known issues. But …
So what are you suggesting, that a developer get a share of whatever "savings" you can calculate for fixing a bad bug?
Sounds like an incentive for developers to deliberately insert bugs and share amongst each other so they can all get fat bonuses for fixing problems they created!
If one guy has a proven history of finding nasty bugs that everyone else overlooks then hopefully he gets a better salary - it would be in his employer's best interests to keep someone like him.
Cassandra is a Key-Value store using column families. That's not the same as a columnar database. They're almost complete opposites, in fact.
>One of the reasons the community was said to have taken so long over the release was the desire to improve quality.
The actual reason is the ASF and Datastax had a big ol' falling out and Datastax took their ball and went home. When the rest of the community didn't follow they sheepishly came back to the fold last year.
Biting the hand that feeds IT © 1998–2022