Depending on the language and context, an explicit method name like "findEventsFromLast6Hours" isn't that bad. If it's just a private helper method, I'd let it pass.
Empirically, I've found that methods with ambiguous parameters (e.g. "findEvents(6)") are a much bigger problem (event amongst senior programmers).
This is very similar to my setup[1]. I picked up a geekdesk frame on craigslist and threw an Ikea countertop[2] on it. I even have a humanscale keyboard tray that I haven't gotten around to installing.
All in all, it probably set me back about $1000 (including the keyboard-tray and monitor-mount). And it was worth every penny; I'm much more comfortable after long hacking sessions.
If you're interested in taking things in the opposite direction, try reducing the prominence of parentheses via ParenFace (http://www.emacswiki.org/emacs-en/ParenFace). I use a very light gray face for parentheses, which is barely visible on a white background.
Details, details. All middle-management cares about is whether or not the task is done. And the associated costs of your shitty code are, at least partially, shifted on to your co-workers. This gives you an even better comparative velocity! Bonus season will be good this year.
It looks like the platform rests on the edges of the masonite. I wonder if it will leave depressions in the hardwood floors underneath? Assuming they don't own the place, their security deposit may help pay for the proper fix.
I use ++i in for loops because pre-incrementing is the semantically correct option. I've never understood why i++ came into favor; can anyone shine some light on it for me?
Generally speaking, this isn't an entirely crazy idea. I'd argue that YC is primarily a networking service too. And it takes a much larger cut from successful startups.
Empirically, I've found that methods with ambiguous parameters (e.g. "findEvents(6)") are a much bigger problem (event amongst senior programmers).