holman

22 ms·

241.
by holman 15y ago
Lanyrd is one of those weird sites that I expect never to work because of how hard it is to consolidate content, and yet it always works. Glad to hear that things are going well for them; without Lanyrd I'm not sure how I'd sort through con
242.
by holman 15y ago
We actually have employees all over the world- Europe, Australia, the US (naturally). And we'd certainly consider hiring globally, but there's some great technologists in SF and we'd just prefer it if you lived/moved out here. Nothing wrong
243.
by holman 15y ago
We'll still work in Campfire though. We have an infrastructure room where we get all of our notices and systems-level logging piped to, and all of our on-call sysops can get together and deal with stuff immediately when it's necessary. But
244.
by holman 15y ago
I have. :) I was more using Taylorism as an example of the notion that he came at it from a physical standpoint: if someone goes to work at the metal factory, their mood has less impact on their productivity than we do at a small startup, b
245.
How GitHub Works: Hours are Bullshit(zachholman.com)
176 points by holman 15y ago|48 comments
246.
Announcing GitHub Issues for iPhone(github.com)
42 points by holman 15y ago|12 comments
247.
by holman 15y ago
I'm forced to download and install all seventy gajillion gigabytes of it in order to get OS X to build anything in different languages like Ruby and Python. I'd love it if I could just download build tools from the App Store rather than ins
248.
by holman 15y ago
You in San Francisco? I'd love to buy you a beer and talk about myself. Serious offer.
249.
Steve Jobs Sometimes Lies to You(zachholman.com)
306 points by holman 15y ago|124 comments
250.
Blog Marketing for Ego-Centric Assholes(zachholman.com)
4 points by holman 15y ago|0 comments
251.
by holman 15y ago
Something I didn't include in the actual post: I don't want to say everything is easy. If one of your goals is to scale your service to a five-hundred box setup, that's probably "hard". But everyone has those vague, important motivations in
252.
Improving Yourself is Easy(zachholman.com)
94 points by holman 15y ago|10 comments
253.
by holman 15y ago
If you're interested in this concept — even (or especially!) for just hacking around on a bored afternoon — Rick Olson gave a fun talk on it last year at RubyConf. "Git: the stupid NOSQL database" http://confreaks.net/videos/443-rubyconf20
254.
Parallaxing Parallax on iOS(zachholman.com)
15 points by holman 15y ago|0 comments
255.
by holman 15y ago
I've sneakily been using this for months on Hacker News itself- I just .hide() stories past around story #15. More signal, less noise. And it's just jQuery, so it's really easy to whip up. Bonus points for it being so easy to share, too: h
256.
by holman 15y ago
We're prepping for a major FI release- expect full GitHub for Mac support at that time. (And yes, FI ships with the full API as well.)
257.
by holman 15y ago
That was pulled from the TomDoc spec- it was designed to demonstrate TomDoc, not the code. Having an overly complicated implementation makes explaining the documentation side of things a bit more difficult. :)
258.
The Most Important Code Isn't Code(zachholman.com)
95 points by holman 15y ago|79 comments
259.
by holman 15y ago
We're definitely in agreement at GitHub. This industry, like every other industry, isn't a zero-sum game; plenty of growth to be had for everyone. This is a nice post, and it's been fun seeing the stuff SF has been building in the last year
260.
by holman 15y ago
I think he had a valid issue and brought it forward in a responsible manner. He's trying to teach Ruby to a classroom of beginners and the first thing you have to tell them is to ignore hundreds of lines of scary-looking deprecation notices
261.
by holman 15y ago
> Then it's the kind of lesson that can be learned from and fixed. No need for forks. I agree. But, to be fair, it's hard to hope for the project to be improved and fixed when someone responsibly brings up the issue on the RubyGems issu
262.
by holman 15y ago
The whole point of versioning, however, is to designate how big changes are between versions. There's a world of difference between 0.2.1 to 0.2.2 versus 0.2.1 and 0.3.0. That's what I'm mostly concerned about- patch versions should be a
263.
by holman 15y ago
I'm all for projects like SlimGems. You can be a cowboy in your app, you can be a cowboy in your framework, you can even be a cowboy in your language , to some extent. But package management should be as absolutely rock-solid and considera
264.
by holman 15y ago
Cool, that makes more sense. I'm satiated!
265.
by holman 15y ago
So you open a tab prior to going to a place, and then the retailer sees all of the customers with recently-opened tabs?
266.
by holman 15y ago
Really stoked about this. I wish they had more details on the process, though. At first exposure, the idea sounds really, really cool. But it sounds like they're breaking the normal purchase loop. Imagine lunch, for example (assuming you've
267.
by holman 15y ago
Hypothetical tweet. It was more for illustrating how retweets can take matters into their own hands, so to speak.
268.
Fame(zachholman.com)
60 points by holman 15y ago|13 comments
269.
by holman 15y ago
I've found that open-sourced websites are less helpful to me, as a developer interested in a project. They're just so complicated- there's a lot of institutional knowledge involved in just navigating the project, much less going into the
270.
by holman 15y ago
Very interesting read. We'll be happy to have our changes pulled into libupskirt proper (and vice versa!) > He then makes a comment on each change s/he/she :)

More ›