I can think of a few ways of how this could backfire / be gamed or abused, but all in all, seeing how everything else is just as susceptible to abuse and gaming, it still sounds awesome to me.
But everything was upside down with that team, not just payment. They had a completely different philosophy when it came to software development.
For instance we were encouraged to just close tasks. It didn't matter what we did as long as the build and code reviewer were happy.
Part of the philosophy was that if developers can abuse and break the project, the project is not good enough and must be toughened. Then, developers were encouraged to find other loopholes.
This methodology worked wonders for small projects, libraries. It didn't go well for big projects, obviously.
This sounds identical to the agency I was reading about.They pay devs for closed tasks. I.e.: a class needs to written that does x. The reward is $100.A senior dev will do it half an hour, while a junior will spend a few hours,which bases work-reward process self balancing based on experience.The owner of the shop had some very detailed blog posts on this,which attracted tons of discussions.Shame I can't recall the guy's name..
It was fun work back in the day of Teamed.io. But nowadays, with Zerocracy, it's turned a bit too strange even for my taste, after having worked about 2 years with Teamed.
If the project isn't a huge bureaucratic nightmare, you can fix those loopholes as they come up. You might even give a small bounty for people who report loopholes. (But make that bounty mostly bragging rights, not money.)
But everything was upside down with that team, not just payment. They had a completely different philosophy when it came to software development.
For instance we were encouraged to just close tasks. It didn't matter what we did as long as the build and code reviewer were happy.
Part of the philosophy was that if developers can abuse and break the project, the project is not good enough and must be toughened. Then, developers were encouraged to find other loopholes.
This methodology worked wonders for small projects, libraries. It didn't go well for big projects, obviously.