stevenwei

I've had a treadmill desk for several years now and haven't noticed any issues with this. It's fine to walk when you're just reading or doing light tasks. I do need to sit when doing concentration heavy work though.

> #Fact: Flappy Bird’s success was because of its user reviews, reaching 700,000 reviews per month

Uh, seriously? Seems like they might have cause and effect reversed there. But at least they marked it #Fact, so clearly it must be true.

This is a blatant advertorial masquerading as advice.

You can, but most of those poor quality treadmills are meant for light use (i.e. running at high RPM for 30-60 mins per day, 3-5 days a week). If you try to run the same treadmill at low RPM for several hours per day every day, you'll burn out the motor pretty quickly.

That's not to say that people don't try though, there are plenty of DIY treadmill desks made out of exactly what you describe.

This is not true anymore. As of August 12, 2014, visa runners will not be allowed back into the country.

Mercedes has been dominant the past two races as well so it's not necessarily a spoiler to say they have been owning the season. On the other hand today's race ended a few hours ago and I didn't expect to run into race results on HN of all places. Oh well.

Aw, a spoiler warning would have been appreciated there.

Perhaps the source is the article itself (i.e. he was contacted by the author)?

I had a bunch of Amtrak points sitting around that I recently redeemed for a bedroom sleeper trip between Seattle and Chicago.

It was an interesting experience but not one that I would repeat. It is by no means a smooth ride, and even with the bedroom I found it quite difficult to get any sleep. Between the horn constantly going off, the bumpiness of the tracks, and the hourly stops/starts, I basically ended up staying awake for 2 days straight.

While I was initially able to get some work done during the trip, after the first night I was way too sleep deprived to be able to continue programming.

But then again, I am a light sleeper, and I have trouble falling asleep on planes too.

Not really. I think the overhead comes more from having to create the views programmatically in the first place.

But once everything is up and running, the maintainability is not very different compared to working with nibs.

We recently converted our project from IB to doing everything programmatically and could not be happier with the result.

As the app has evolved over time and grown in complexity, we felt we reached a tipping point where using IB was slowing us down more than it was helping. Same for auto-layout.

Part of this was because the app simply has a lot more functionality today than it did three years ago, which means there were a lot more nibs to manage than before. Part of it is because we started developing more custom views that did not map to any existing IB components and thus had to be done by hand anyway. Part of it is because we found we had to switch to drawing certain things programmatically for performance reasons. Either way, I'm quite glad we made the conversion.

That said, I agree that most apps should start with IB and only move onto the more complex stuff once/if the need arises. IB helps a lot out of the gate (and also makes learning the platform a lot easier since you can visually see what you're setting up). Once it gets to be a hindrance, you'll know, and you can then make the decision to switch later on. And if your app goes nowhere, then you'll have wasted less of your time.

I also strongly agree that explicit is better than implicit, and configuring a view programmatically allows you to fully specify what its behavior should be, rather than what it happens to be. When you revisit a nib several months later after originally configuring it, sometimes you forget whether the configuration option you selected in the dropdown was intentional, or was it the default, or was it merely accidentally changed at some point?

[blue][red], you want to make sure you round their shared edge either to the left or to the right. Otherwise, there will be a gap between them. You need to make sure you round their shared edge the same way consistently too, or it will jump back and forth as you resize a window and produce a noticeable jitter.

In this case I would probably do something like:

    red.left = blue.right;

(Or vice-versa, depending on which edge you are positioning against).

Luck is also a huge factor. Sometimes it's just one of those 'right place, right time' moments that can't really be replicated again.

They are technically called distributions, not dividends, for the reasons you mentioned.