2 ms·
I think thats reasonable. Mission aside, this is only going to work if you get solid PRs that are easy to merge. Even with no cost if no merge, there is still a
by hzia 3y ago
I think thats reasonable. Mission aside, this is only going to work if you get solid PRs that are easy to merge. Even with no cost if no merge, there is still a high opportunity cost if your team reviews a PR and doesn't merge it.
Which is why we actively monitor review cycles as our biggest metric internally to make sure quality is solid across all active repos.
- brap 3y agoI understand, but my point is that your landing page should focus on just that, value for money. All the other stuff is nice, but it’s not going to sell. It might actually be detrimental.
- hzia 3y agoAgreed ... the service itself has to hold ground on its own. Thats why on our landing page, the focus is on the service itself with some mission interleaved. Would you reckon it's the right balance?
- brap 3y agoI would respectfully disagree. You gotta look at this from your customers’ perspective. All they care about is that using your service means quality work for less cost. The more you talk about other things, the more they’re going to question the quality of the work they get in return. So even though it’s a noble goal, I wouldn’t mention it at all to customers. Where I would emphasize it is where you onboard devs to your platform, since they care about their own personal grown. Or when you hire people for your company, since people like working for a good cause. Or maybe if you’re trying to score some grant. Perhaps even some investors care, depends on the person. But customers? Nah. They have other problems to worry about.