News for hackers. Stuff that matters.

bkeepers

bkeepers on Hacker News

Re:GitHub announcements: Marketplace, Apps and GraphQL API on Monday May 22, 2017 @08:29AM (#14392981)
We don't have a timeline yet, but any updates will be posted on the API blog: https://developer.github.com/changes/
Re:GitHub announcements: Marketplace, Apps and GraphQL API on Monday May 22, 2017 @08:21AM (#14392929)
GraphQL will be available in GitHub Enterprise 2.10, and GitHub Apps will be available in 2.11. For Marketplace, we will be researching how to solve similar problems for Enterprise customers after this initial launch.
Re:GitHub announcements: Marketplace, Apps and GraphQL API on Monday May 22, 2017 @07:14AM (#14392543)
GitHub Apps also support authenticating users with OAuth, so you might want to check out if it makes sense to migrate.

https://developer.github.com/apps/building-integrations/sett... https://developer.github.com/apps/building-integrations/sett...

Re:Announcing Open Source Guides on Monday February 20, 2017 @01:41PM (#13689747)
PR where domain was purchased: https://github.com/github/open-source-guide/pull/90
Re:Introducing unlimited private repositories on Wednesday May 11, 2016 @03:59AM (#11673412)
We are reaching out to customers that are in unique situations such as the one you're mentioning here. If you have questions about how the pricing changes affect you, please don’t hesitate to contact [email protected].
Re:Introducing unlimited private repositories on Wednesday May 11, 2016 @03:42AM (#11673336)
An individual on the Personal plan can add users to their private repositories for free.
Re:Introducing unlimited private repositories on Wednesday May 11, 2016 @03:29AM (#11673269)
Outside collaborators count towards a seat on private repositories and are free on public repositories.
Re:Introducing unlimited private repositories on Wednesday May 11, 2016 @03:24AM (#11673231)
Good question! Students get free private repositories for 2 years. You can request the student discount at https://education.github.com/
Re:Lessons learned from a cancelled project on Monday April 28, 2014 @12:52PM (#7661158)
The biggest difference is that our "PRPs" don't see management as their primary responsibility. They're still an engineer or designer first.

> Every successful startup eventually discovers that the O(n^2) communication overhead of a perfectly flat org doesn't scale, and needs to adapt to deal with that. The question is whether to develop coordination specialists implicitly or explicitly.

Yep. This is certainly something we feel the pain of and are wrestling with right now.

> Developing doublespeak to protect an idealistic worldview from its incompatibility with reality does seem pathological.

By definition, we don't have anyone that plays the role of "manager" right now (again, for better or worse). I wouldn't call that doublespeak.

Re:Lessons learned from a cancelled project on Monday April 28, 2014 @11:25AM (#7660543)
You are right. For better or worse, we have not had traditional PMs at GitHub. Often that is a role played by what we call a PRP (primarily responsible person). That person is often an engineer or designer.
Re:Expanding Context in Diffs on Tuesday December 03, 2013 @02:24PM (#6842476)
https://github.com/blog/1707-soft-wrapping-on-prose-diffs

In your honor, I used an example from the cryptoparty handbook. Cheers!

Re:What's it like to work at GitHub? on Wednesday June 06, 2012 @07:28AM (#4073226)
That's a question I hear often, or another form of it: "How do you get people to do things that nobody wants to do?" I usually answer this with two questions:

1. If everyone deeply cares about the culture and longevity of the company (which is a prerequisite), and nobody wants to do it, does it really need to get done? The answer is often no. But if the answer is yes…

2. How do you turn that into a celebrated task where everyone wants to do it?

One example of this at GitHub is support. Developers hate doing support. But we have decided that it is absolutely vital to our company to both provide good support and to have developers involved in it so we are constantly getting feedback about what is working and what is not.

So we created the "King of Developers", which is a position that is held by a developer for one week at a time, in which that developer's primary responsibility is support. Along with that comes a pimped out desk at our HQ in San Francisco and tons of street cred. We even have a ridiculous internal website to go along with it (http://dribbble.com/shots/554836-GitHub-King-of-Developers). There are currently 9 developers signed up waiting to be the King.

Re:What's it like to work at GitHub? on Tuesday June 05, 2012 @11:59AM (#4069171)
We have the advantage of using GitHub to build GitHub (http://zachholman.com/talk/how-github-uses-github-to-build-g...), so we all know what needs worked on. There is certainly some vision casting from a few core people, but everyone takes responsibility for figuring out what needs done and coordinating how to do it.

> Who makes these decisions, when there are multiple viable ways of going forward, but someone just has to put their foot down and decide which one?

We all do, but whoever submits the first pull request usually sets the tone of the conversation. Occasionally, a pull request will get abandoned, but usually it is the starting point and we build from there.

There are often intense conversations about how something should work. I've learned to just try one way and see if you like it. Not everyone will, but you can form some consensus.

Re:Getting Started with Sublime Text 2 on Thursday January 12, 2012 @11:03AM (#3456763)
I agree, I like the new default theme a lot better. Good work! I updated the original post.

Older »