4 ms·

I'm confused about the pricing. The pricing page shows this PR as an example of a "small" PR of 15 "credits". I have a hard time agreeing that this change is wo

I'm confused about the pricing. The pricing page shows this PR as an example of a "small" PR of 15 "credits". I have a hard time agreeing that this change is worth $150: https://github.com/calcom/cal.com/pull/8218/files https://github.com/calcom/cal.com/pull/8218/files 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?

michaelt 3y ago
A Silicon Valley developer on $200,000 costs $100/hour in salary alone. 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.
- rsstack 3y ago
  But they're not offering Silicon Valley developers, the comparison is moot.
  - michaelt 3y ago
    No, but to clients accustomed to paying Silicon Valley prices $150 isn't too bad, if the tickets get closed. If you look on sites like Upwork, even developers from poor countries often cost $30+ per hour.
hzia 3y ago
Did you go through the PR discussion though? 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.
- sdesol 3y ago
  > In this particular case there was technical discovery on a non-trivial approach to patch an npm package (which didn't work out) 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-age%3A%3C%3D120&bt=closed&q=calcom%2Fcal.com%3A8218&t=crc-insights-pom-changes&v=calcom%2Fcal.com%3A%3Agithub%3Acalcom%2Fcal.com%3A%3A%3A%3A https://reviews.gitsense.com/insights/github?bq=8218%2Bpull-... Full Disclosure: This is my tool
- rsstack 3y ago
  To be honest, I didn't until now. The first six comments are automated, and I stopped scrolling fairly quickly. My bad, and I'll quietly be mad at the state of the GitHub PR "discussion" tab that has just too much spam in it. 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.
  - hzia 3y ago
    GitHub PR detail view is a hot mess. The entire page is endlessly long, with very poor signal to noise ratio 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
- laweijfmvo 3y ago
  How much (out of that $150 e.g.) does the developer get and how much does GitStart keep?
  - ActionHank 3y ago
    This is the crux of the issue. 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.

michaelt 3y ago

A Silicon Valley developer on $200,000 costs $100/hour in salary alone. 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.

rsstack 3y ago
But they're not offering Silicon Valley developers, the comparison is moot.
- michaelt 3y ago
  No, but to clients accustomed to paying Silicon Valley prices $150 isn't too bad, if the tickets get closed. If you look on sites like Upwork, even developers from poor countries often cost $30+ per hour.

hzia 3y ago

Did you go through the PR discussion though? 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.

sdesol 3y ago
> In this particular case there was technical discovery on a non-trivial approach to patch an npm package (which didn't work out) 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-age%3A%3C%3D120&bt=closed&q=calcom%2Fcal.com%3A8218&t=crc-insights-pom-changes&v=calcom%2Fcal.com%3A%3Agithub%3Acalcom%2Fcal.com%3A%3A%3A%3A https://reviews.gitsense.com/insights/github?bq=8218%2Bpull-... Full Disclosure: This is my tool
rsstack 3y ago
To be honest, I didn't until now. The first six comments are automated, and I stopped scrolling fairly quickly. My bad, and I'll quietly be mad at the state of the GitHub PR "discussion" tab that has just too much spam in it. 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.
- hzia 3y ago
  GitHub PR detail view is a hot mess. The entire page is endlessly long, with very poor signal to noise ratio 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
laweijfmvo 3y ago
How much (out of that $150 e.g.) does the developer get and how much does GitStart keep?
- ActionHank 3y ago
  This is the crux of the issue. 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.