Scaling GitHub's Employees
zachholman.com
Scaling GitHub's Employees
1–10 of 40 posts
Re: Scaling GitHub's Employees
#2If only they could scale their sales department. We've received no response for 2 weeks using 3 different methods of contacting them.
Re: Scaling GitHub's Employees
#3If only they could scale their sales department. We've received no response for 2 weeks using 3 different methods of contacting them.
Doesn't look like anything's two weeks behind on our end; might've gotten lost in the mix. I assume you already did this, but can you shoot us an email at support@github.com (or sales@github.com for FI sales) and we'll make sure to get on it. You can cc zach@github.com too, just in case, and I'll keep tabs on it personally.
Re: Scaling GitHub's Employees
#4If only they could scale their sales department. We've received no response for 2 weeks using 3 different methods of contacting them.
I'm guessing you'll get a response now since more of their 40 employees probably check HN than they do the sales email :)
Re: Scaling GitHub's Employees
#5If only they could scale their sales department. We've received no response for 2 weeks using 3 different methods of contacting them.
Doesn't look like anything's two weeks behind on our end; might've gotten lost in the mix. I assume you already did this, but can you shoot us an email at support@github.com (or sales@github.com for FI sales) and we'll make sure to get on it. You can cc zach@github.com too, just in case, and I'll keep tabs on it personally.
I haven't had to contact sales, but I can vouch for your responsiveness at support@github.com
I've emailed you guys a few times and received 1 hour turnaround with complete resolution, day or night.
Thanks!
Re: Scaling GitHub's Employees
#6If only they could scale their sales department. We've received no response for 2 weeks using 3 different methods of contacting them.
Doesn't look like anything's two weeks behind on our end; might've gotten lost in the mix. I assume you already did this, but can you shoot us an email at support@github.com (or sales@github.com for FI sales) and we'll make sure to get on it. You can cc zach@github.com too, just in case, and I'll keep tabs on it personally.
Thanks for the feedback! We've tried calling the sales phone number, filling out the web form and emailing sales@github.com, all with no response, so we were starting to give up hope ;)
Re: Scaling GitHub's Employees
#7Don't get me wrong, I love GitHub and I love the processes they are using - I wish we did more of it at my current employer. But all of this back-patting feels a bit premature. They've really only scaled a single order of magnitude. Growing from 4 developers to 40 developers is excellent, but hardly "scaling" at all. Would the same flow work at Amazon, Netflix, or Apple?
Re: Scaling GitHub's Employees
#8Don't get me wrong, I love GitHub and I love the processes they are using - I wish we did more of it at my current employer. But all of this back-patting feels a bit premature. They've really only scaled a single order of magnitude. Growing from 4 developers to 40 developers is excellent, but hardly "scaling" at all. Would the same flow work at Amazon, Netflix, or Apple?
I'd argue that how you go from 4 to 40 developers is much more important than how you go from 100 to 200 developers. What's more, I find this area fascinating to discuss since many users in our Hacker News community tends to be in the 1-10 developer area. How you can grow past that initial team is really important.
I do actually mention at the end of the post that this likely doesn't scale up to hundreds and employees. But we'll see how it does work over time. So far so good. :)
Re: Scaling GitHub's Employees
#9Don't get me wrong, I love GitHub and I love the processes they are using - I wish we did more of it at my current employer. But all of this back-patting feels a bit premature. They've really only scaled a single order of magnitude. Growing from 4 developers to 40 developers is excellent, but hardly "scaling" at all. Would the same flow work at Amazon, Netflix, or Apple?
the last paragraph of the article is an adequate response to this:
"Is this workflow going to work for us when we’re 500 employees? Likely not. But core values and ideas last. Figure out what your core values are, and adapt and refine them as you grow."
Re: Scaling GitHub's Employees
#10these series of posts about how they do stuff is great, i love it.
however, dreaming up the end result is a lot easier than figuring out what seeds to plant when you are a team of 1 or 2. after reading these i'm always left with the question "great, but what should i be doing now to be able to have this kind of process later?"
maybe the answer is in the article: figure out your core values and start applying them at whatever scale you are at. alas, that's not a list of actionable items.