News for hackers. Stuff that matters.

jbarnette

By the time we extracted Scientist, the code we were refactoring had pretty good test coverage. But even the best test suite is an imperfect model of production. The first section of the README briefly mentions this:

"Let's pretend you're changing the way you handle permissions in a large web app. Tests can help guide your refactoring, but you really want to compare the current and refactored behaviors under load."

Thanks, Evi. You were kind to me when I was very young and very stupid.
Re:Kubernetes at GitHub on Thursday August 17, 2017 @07:43PM (#15042111)
EY, Rackspace, and then our own metal.
Re:State of the Octoverse 2013 on Wednesday February 05, 2014 @10:56PM (#7188642)
Pretty much only the early employees remember where that humans.txt is stashed.
Re:State of the Octoverse 2013 on Wednesday February 05, 2014 @09:41PM (#7188401)
I wouldn't be surprised if a few GitHubbers dropped by Huntsville sometime this summer. Watch the blog.
Re:Google Analytics for GitHub on Tuesday January 07, 2014 @02:28PM (#7019281)
We'll see what we can do. ;)
Re:How GitHub No Longer Works on Thursday November 14, 2013 @08:51PM (#6737194)
There is no such thing as a shit task.

Added: That's a little too glib, sorry. Let me try again: From my perspective, if there's something that needs to be done at GitHub there are a few possibilities:

1. It needs to be done and it's getting done,

2. It needs to be done and it's not getting done, or

3. It's bullshit.

Cases of #3 become obvious pretty quickly. The best evidence: Searching for ways to make someone do it because nobody stepped up.

Cases of #2 can happen for a bunch of different reasons, but malice, apathy, laziness, or incompetence are the least likely ones. The most likely: Not enough hours in the day or not enough people with the knowledge necessary to be worried. No matter the reason for #2, someone at GitHub who is worried will generally try to get others to share their priorities, by persuasion, by hiring, or by prototyping.

Or occasionally by just jumping up and down and wailing.

Re:How GitHub No Longer Works on Thursday November 14, 2013 @03:49PM (#6735453)
We use PRP in any situation where someone explicitly takes responsibility for an outcome, no matter whether the outcome is some software or a clean office or an accurate tax return.
Re:Identicons on Wednesday August 14, 2013 @06:08PM (#6214672)
If you're running a recent version of GitHub Enterprise, the avatar base URL can be configured today. It's possible to run an internal, secure server that responds to Gravatar's URL scheme.
Re:More Git and GitHub Secrets on Thursday July 25, 2013 @12:04AM (#6100850)
We released task lists earlier this year: https://github.com/blog/1375-task-lists-in-gfm-issues-pulls-...
Re:GitHub's on your phone on Monday July 15, 2013 @05:41PM (#6048728)
Yup, we're focusing on the pages most likely to be clicked through on mobile first.
Re:Free private Github repos for students and edu people on Thursday May 23, 2013 @10:07PM (#5760848)
Have you asked us? support@github are real humans, I promise.
Re:Free private Github repos for students and edu people on Thursday May 23, 2013 @10:04PM (#5760838)
I'm really sorry to hear that. I work at GitHub, so if you want to talk more about your experience please drop me a line. It's this username at that domain. Or hit up any other GitHubbers in this thread: We wouldn't be hanging around if we didn't want to hear from you.
Re:Github turns five on Thursday April 11, 2013 @03:12PM (#5534088)
NilClass.
Re:Github turns five on Thursday April 11, 2013 @03:11PM (#5534072)
It's in the early 7000's.
Re:STL File Viewing on Wednesday April 10, 2013 @02:40AM (#5523566)
We grabbed a 3D printer for the office a while ago.
Re:Introducing Boxen on Friday February 15, 2013 @03:56PM (#5228611)
Drift after installation and incremental updates were more of a problem for us than initial installs.
Re:Introducing Boxen on Friday February 15, 2013 @03:36PM (#5228465)
We've opened up #boxen on freenode for questions and discussion. We'll idle there whenever we can.
Re:Ruby inline assembler on Friday January 11, 2013 @11:34AM (#5043386)
My favorite thing about this library is that it parses the NASM manual: https://github.com/seattlerb/wilson/blob/master/lib/wilson.r...
Re:Introducing Contributions on Monday January 07, 2013 @07:11PM (#5024136)
Yep, we don't count contributions until they hit a repository's default or gh-pages branch.
Re:GitHub now has Issue Attachments on Friday December 07, 2012 @03:26PM (#4889082)
We don't have roadmaps or a prioritized backlog, so we weren't exactly "waiting" to implement this. Someone got fed up with the image workflow, figured out a solution, grabbed some other people to help, and shipped it.
Re:GitHub now has Issue Attachments on Friday December 07, 2012 @02:41PM (#4888844)
Yup, images only.
Re:The GitHub hiring experience on Tuesday September 25, 2012 @02:39AM (#4568970)
There are a fair amount of us > 35 folks at GitHub.
Re:What's it like to work at GitHub? on Tuesday June 05, 2012 @08:49PM (#4071818)
GitHub has been organized this way since it was in a pre-revenue state.
Re:Diaspora Co-Founder Ilya Zhitomirskiy Passes Away At 21 on Sunday November 13, 2011 @06:29PM (#3232132)
We started doing this in Seattle last year with some success (http://startupsanonymous.com). I've kept it dormant during a busy move to New Orleans, but if anybody's interested in working together to get it started again I'm up for it. There's a need.
Re:ROC, a Redis Object Collection for Ruby on Tuesday August 16, 2011 @09:52AM (#2891122)
https://github.com/nateware/redis-objects is clean, mature, and has worked very well for us in several production systems. What makes ROC better?
I don't get the impression that many of the commenters here are spending a lot of time trying to hire good people right now. I am, and I'd be grateful to receive an email like this.

I wouldn't like it, but honest, personal feedback on an interview process is hard to find.

Re:Review My Startup: ZestyLogos on Tuesday October 26, 2010 @12:26PM (#1834823)
There are some good sample logos on the page, but the overall design reads more as a vanity site/portfolio than as a marketing page.

Make every element on the page justify its presence. "Hey, coffee-stained TODO list in the top right corner, why do you exist? How are you helping me sell logos?"

Consider finding someone to do a thorough edit of your marketing copy. Lots of good ideas in there, but it's uneven.

Re:ARel 2.0: Active Record Performance in Rails 3.0.2 on Friday October 15, 2010 @11:31AM (#1794882)
Aaron's real blog: http://tenderlovemaking.com

Older »