When seeing $10/credit, I thought a PR this small would be just one or two credits. I'd totally pay $150 to fix 10-15 such small bugs, but only one? Am I missing something?
In this particular case there was technical discovery on a non-trivial approach to patch an npm package (which didn't work out)
But above aside, one can get a lot more milage out of GitStart if small fixes are bundled together. As that means all of them share the cost of QA (across devices), bundled code review and less context switch overhead.
I'm glad you wrote your last paragraph! I did wonder how much of the credits cost was just overhead as the costs of small/medium/large are fairly close to each other. It makes sense to me.
We are very tempted to re-build that experience on the dashboard(at-least for our PRs), but I hope someone can launch a simple dashboard a better UX to replace the current PR detail view
The whole product disenfranchises upcoming junior devs of their potential earnings and credit for their efforts. "I built and shipped product X which generated Y revenue for company Z" read better than "I worked on a series of PRs across many different products with little insight to the product as a whole or much say in the technical direction".
This sort of thing will likely reduce number of devs that move on from junior to senior long term and put people off of joining the industry overall.
You can see that this PR took a while to get merged (~2 months) with multiple iterations as shown here https://reviews.gitsense.com/insights/github?bq=8218%2Bpull-...
Full Disclosure: This is my tool
When your employer onboards new hires, do they have a commit merged into main in their first 90 minutes with the company?
Software development is an expensive business, and some companies are used to paying this much and more. The no-fix-no-fee pricing model would also command a premium over hourly work.
If you look on sites like Upwork, even developers from poor countries often cost $30+ per hour.