holman

23 ms·

181.
by holman 14y ago
Nothing! In fact, the new issue attachments code uses plain ol' Markdown to show the image. The reason we added this is because arcane Markdown code is impossibly hostile for new users and beginners.
182.
by holman 14y ago
Ops has been at the core of what GitHub does pretty much since day one. I'm not sure there's a team more celebrated within GitHub as our ops guys, to be honest.
183.
by holman 14y ago
Not that one. :) Just took a random URL and truncated a few numbers. Didn't want to tie it to anything in particular.
184.
by holman 14y ago
Good point. This talk got restructured at least twice this week before I gave it, but I should have reworded those phrases, too.
185.
by holman 14y ago
But it'll also give me a longer deadline than a couple months (which is important when it's a side project that I don't want to dedicate a lot of time to).
186.
by holman 14y ago
Pro tip: if, like me, you have an ancient app on Aspen and moving it to Cedar sounds like a horrible, horrible transition, just switch it to Bamboo instead. Buys you some more time to put it off until they sunset that too.
187.
by holman 14y ago
Man, that's pretty pessimistic. If you want the straight dope — or maple syrup, in your case — here it is: hiring good people is the most important thing we do, and we don't fuck around with that. We fly people in, get them to meet people
188.
by holman 14y ago
It depends. Most employees are going to experience slower than four days- hiring can be difficult (not only because of trying to find the right person, but because arranging things in meatspace like phone interviews and flights and schedule
189.
by holman 14y ago
This seems pretty silly. A lot of people — myself included — use photos as a way to remember something. Occasionally I'll take a photo of food or the restaurant or something around me just to remind me of that experience; reliving my life t
190.
by holman 14y ago
Generally, Git will be way too slow for that. Git is typically our bottleneck, since you're dealing with so much overhead and disk access to perform functions. Databases are best for, well, performing relational queries. In the case of comm
191.
by holman 14y ago
Rumor is that it's in the works.
192.
by holman 14y ago
My visceral reaction to the idea of one giant room was "Rad". Love open floor plans. I'm really curious what the final interior plan will look like; presumably it's not some huge airplane hanger of openness but some clever way of staying op
193.
by holman 14y ago
Admittedly I slipped an "always" in there when I shouldn't have; I agree that anticipatory talks can be great, too. Let's put it this way, though: for a beginning or first-time speaker, I'll maintain that talks should be reactionary. There
194.
by holman 14y ago
You still missed yesterday's bump. It'll be less than a year.
195.
by holman 14y ago
Actually, it hasn't been four years between updates: http://buyersguide.macrumors.com/#Mac_Pro The Mac Pro had updates in 2008, 2009, 2010, and yesterday. They may not be the type of pie-in-the-sky updates you might want, but that's anoth
196.
by holman 14y ago
We've been splitting up into teams (or roles) a bit more as we've grown- it just helps to keep the focus on things that matter. That said, the most important part about this is that those teams are extremely weak. In other words, you should
197.
Git and GitHub Secrets(zachholman.com)
27 points by holman 14y ago|0 comments
198.
by holman 14y ago
We noticed a problem with it after deploying- just working out a few kinks with it before we ship it again.
199.
by holman 15y ago
We tend to stay under 80c for everything (minus views, which can be trickier). Probably should add that to the guide.
200.
How GitHub Works (Slides)(zachholman.com)
13 points by holman 15y ago|0 comments
201.
by holman 15y ago
GitHub's listed as an example, but I don't really think we should be. It was pretty reasonable for us to start on virtualized instances to start out. By the time we moved to bare metal, we had grown quite a bit and it was pretty clear what
202.
by holman 15y ago
We will never, ever suspend or ban accounts that follow responsible disclosure. Ever.
203.
by holman 15y ago
It's a lot quicker to publicize a vulnerability than it is to patch, ascertain the scope, and verify the current situation. We're taking the time to make sure the information we'll relay to you is accurate.
204.
by holman 15y ago
We've patched and fixed this on GitHub.
205.
by holman 15y ago
Could be! The article itself is open source, too: https://github.com/WiredEnterprise/Lord-of-the-Files
206.
by holman 15y ago
Our office communication is fairly nonexistent. Everything's done through chat, so you're not missing much if you're in the office or not or in the quiet area of the office. And the music choice isn't really enforced... we built a shared mu
207.
by holman 15y ago
Like I said, go into one of the private offices. Or don't go into the office.
208.
by holman 15y ago
This depends on where you're working. If you're looking for efficiency, sure, maybe open plan offices will impact your Business Efficiency Quotient. If your company enjoys having an open floor plan, then just do it. When in doubt, value hap
209.
by holman 15y ago
Keynote. You might be interested in: http://zachholman.com/posts/slide-design-for-developers/ https://github.com/holman/feedback/issues/71
210.
by holman 15y ago
Our deployment process operates outside of our traditional network setup. If, for example, we push a change that breaks repository serving for everyone on github.com, we still deploy as normal and won't be impacted by it.

More ›