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.
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.
If you're largely sedentary, getting an hour of exercise per day doesn't counteract the fact that you've been sitting for 12 hours per day. [1]
Simultaneously, walking slowly all day does not burn many calories compared to a proper workout. But that's fine, because the goal of walking slowly all day is not to burn calories, but simply to keep you from sitting all day.
It seems to me the best approach is to simply do both.
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.
The desk itself is electric height-adjustable which makes it easy to switch between walking/standing and sitting with the push of a button, and the monitors are mounted on arms so I can move them to the correct height when I switch positions.
It took some getting used to before I could walk for extended periods of time, but now I don't really think about it anymore, I just start walking and before I know it, an hour has gone by. That said, I have found that it's hard to really concentrate while walking. If I find myself in the middle of a particularly difficult programming problem, I'll often need to sit down before I can really think about it.
But there's a lot of time throughout the day where I'm not doing anything that's super mentally challenging, like reading HN :) or catching up on email or finishing light programming tasks, and I try to walk as much as possible during those times.
At this point I typically walk between 1-3 hours total per day, and end up alternating between walking/standing/sitting every hour or so. Sometimes after sitting for a while I find myself starting to feel sleepy, switching to walking at this point usually wakes me right back up and keeps me going. Not sure, why, probably a circulation thing.
The setup wasn't particularly cheap to put together (though you could certainly do it for a lot cheaper than I did), but after a year I've concluded the cost was totally worth it considering how many hours of my life I spend (and will continue to spend) in front of a computer.
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.
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).
These are very interesting numbers. Obviously the financials are not well suited to the VC-backed startup model, but I wonder if Everpix could have been successful as a small business run by a small handful of people.
I'm a huge fan of the Prana Brion (http://www.prana.com/brion-pant.html) - very similar to the one you linked, except without the cargo pockets. After getting these I'm never going back to pants without stretch fabric or water resistance. They're great for travel and in charcoal they look reasonably dressy too.
It doesn't make any sense to add up the highest marginal tax rates like that though.
In your example of someone earning $90k in CA, the federal income tax rate of 28% only applies to the $2150 of income above the threshold of $87,850, the rest is taxed at lower rates according to the lower brackets. The same applies to state taxes, except the brackets are different.
The effective tax rate (e.g. the total amount of tax you pay / your total income) has a lot more meaning, and that one is a lot lower than 50%.
The original claim that started this thread, "Personal income taxes are about 50% in the US", is not true at all.
On top of this, if you are making any significant amount of money as a self-employed individual you should probably look into setting up a solo-401k or a SEP-IRA, which will help reduce your taxable income (by up to $51,000 for 2013).
These numbers are heavily skewed by the fact that the Top 200 on both iOS and Android are dominated by IAP based games. E.g. Candy Crush Saga and Clash of Clans are not significantly different on iOS vs Android, and that is where the narrowing gap is coming from.
But for independent app developers (particularly those making paid apps), the numbers that I've seen from many folks (and also from personal experience) are strongly weighted towards iOS. Every single developer I've talked to who has released an app on iOS and Android has come to the same conclusion: Android users simply don't pay for apps.