Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: PullRequest (YC S17) – On-Demand Code Review

news.ycombinator.com

Post reply on HN
Print view View original

61–68 of 68 posts

Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review

#61

Post by lyal »

hitgeek wrote: post #53
jlamberts wrote: post #26

I would love this as an individual when learning new languages on my own projects. I find it really hard to tell if I'm actually doing things the "right" way without talking to someone more experienced.

yes this is a good thought. I wish they had a free tier for this purpose. 1 review a month or something.

We would love to offer one review a month - unfortunately, because there are humans on the other side of the review, it's harder to do this than for a straight SaaS operation.

We'll definitely have free tiers for our static and instrumentation product though.

Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review

#63

Post by lyal »

edraferi wrote: post #28
lyal wrote: post #27

Earlier quoted context omitted.

We have a few folks that have signed up for just this! I think it's a neat concept.

Took another look at the pricing page and saw "billing is dependent on amount of meaningful change per month. $9 per user per month for static analysis." Does that mean I could expect to pay Might be worth clarifying the pricing description.

Thanks for the insight. We'll definitely be clearing up the pricing packages.

Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review

#64

Post by pj_mukh »

I am very interested in a product like this even if for just individual use. Your pricing says $49/month depending on "meaningful" changes suggested? What does that mean?

Another good idea is for new programmers in a production environment just having an eye over their shoulders making sure they aren't making rookie language mistakes (simpler ways of doing etc.). Letting official company engineers focus on architectural/roadmap related issues.

This, to me, would be the fastest way to learn as well.

Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review

#65

Post by lyal »

pj_mukh wrote: post #64

I am very interested in a product like this even if for just individual use. Your pricing says $49/month depending on "meaningful" changes suggested? What does that mean? Another good idea is for new programmers in a production environment just having an eye over their shoulders making sure they aren't making rookie language mistakes (simpler ways of doing etc.). Letting official company engineers focus on architectu…

We price based on the amount of review being done per month. $49 is the base threshold; individual reviews can vary based on the amount of code being reviewed at once. We're figuring out the exact pricing model for individuals and teams that'll be easily communicable.

Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review

#66

Post by kevinSuttle »

lyal wrote: post #12
kevinSuttle wrote: post #11

Earlier quoted context omitted.

This is a big opportunity to create an entirely new specialized role. Could be very lucrative for people to make names for themselves.

Completely agree! The idea of a 10x reviewer has been a big part of my thinking on creating this company (and the movement of specialization for review out of big tech companies into smaller engineering teams).

Great idea. Admittedly, I didn't get it at first, but I'll be watching your progress now that I see it. Good luck!

Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review

#67

Post by LrnByTeach »

danpalmer wrote: post #8

Roughly speaking, I think there are 3 aims for code review: 1. Style/consistency, re-use of existing code, utils, etc. 2. Architecture/design, how does this fit into the rest of the codebase, scaling concerns, how will the deploy work, will this have race conditions, etc. 3. Knowledge sharing with other members of the team. Currently, it looks like this would satisfy half each of 1 and 2, but will miss the (possibly…

> 3 aims for code review:

> 1. Style/consistency, re-use of existing code, utils, etc.

> 2. Architecture/design, how does this fit into the rest of the codebase, scaling concerns, how will the deploy work, will this have race conditions, etc.

> 3. Knowledge sharing with other members of the team.

> Currently, it looks like this would satisfy half each of 1 and 2

In my opinion, Even a service that address the 1) and 2) add lots of value for so many IT projects (out side of cutting edge Startup companies )

Re: Launch HN: PullRequest (YC S17) – On-Demand Code Review

#68

Post by lamby »

LrnByTeach wrote: post #67
danpalmer wrote: post #8

Roughly speaking, I think there are 3 aims for code review: 1. Style/consistency, re-use of existing code, utils, etc. 2. Architecture/design, how does this fit into the rest of the codebase, scaling concerns, how will the deploy work, will this have race conditions, etc. 3. Knowledge sharing with other members of the team. Currently, it looks like this would satisfy half each of 1 and 2, but will miss the (possibly…

> 3 aims for code review: > 1. Style/consistency, re-use of existing code, utils, etc. > 2. Architecture/design, how does this fit into the rest of the codebase, scaling concerns, how will the deploy work, will this have race conditions, etc. > 3. Knowledge sharing with other members of the team. > Currently, it looks like this would satisfy half each of 1 and 2 In my opinion, Even a service that address the 1) and 2…

> Even a service that address the 1) and 2) add lots of value for so many IT projects

Especially when they currently have no existing code review.

Post reply on HN