There is a huge difference between founding a startup in the midwest and being an engineer in the midwest. I believe that gets lost in a lot of the rhetoric from both sides. I love hiring engineers in the midwest. Consistently great work ethics, etc, etc.
On the other hand, if you're an entrepreneur, you don't live in SF and you're building a consumer internet startup, you're fucked. Primarily because your access to capital is so limited it's ridiculous. Most people that live in the midwest aren't able to put in the time required to build out the relationships needed to successfully fundraise in the Valley.
The other side of the coin: If you live in SF and your VC backed startup doesn't experience massive growth then you're fucked. In a cheaper city you can be ramen profitable, or a lifestyle business, or just a regular business or whatever.
Cutting calories is the only way to lose weight. Cutting carbs typically means people end up eating less calories, because protein is more satiating.
"Eating the same diet, just a lot less carbs"
If you're eating less carbs, that's 4 calories less for every grab of carbs you've cut out. If previously you were eating around 200g of carbs everyday (probably on the low end, honestly) you've now removed around 800 calories from your diet.
I hope you aren't suggesting that the only ways to lose weight are by lowering intake of calories below your daily usage, or increasing your daily usage of them above your daily intake through some form of additional calorie burning activity...
(cause you'll never sell a best-selling book like that)
I think only the kookiest diets ignore this basic principle. The problem is that most people can't just rationally decide "oh I'll just eat less" or "I'll just eat lower-calorie foods" or "I'll just exercise a lot more and ignore the hunger that comes with it". Well, you can decide that for a variable-length but generally short amount of time, and then billions of years of evolution kick in and hormones make you want to eat more, and eat all kinds of stuff your rational mind tells you is probably a bad idea, but maybe just this once.
Dieting is about tricking that system in one of various ways. Different things work for different people. For some people, no tricks are required but you can't just assume it's that easy for everyone.
The number of calories you burn isn't just a minor detail you can brush away.
Some sources of energy turn preferentially into fat, others promote a higher burning base metabolism. And when you say weight, you're ignoring other factors like muscle mass, water retention, others, that aren't really what we mean when we say lose weight. (Although incidentally, cutting carbs decreases water retention which is one very valid counter to the low-carb weight loss claims.)
Ignoring the very direct counter-statement by OP that he increased his caloric intake and still found success cannot be dismissed.
There are other ways to lose weight. Such as swallowing tape worms, taking a laxative with every meal, using meth, moving to the moon... The statement "Cutting calories is the only way to lose weight" is a gross oversimplification and provably false.
It isn't that simple and a group of us has proved that isn't necessarily true.
Three times I have lead several people through the Whole30 Challenge laid out the Whole9 website mentioned above. We all ate a ton of food and lost fat and almost all of us lost weight. If anything, our caloric intake stayed the same or went up.
(BTW: the goal wasn't to lose weight. It was to become healthier. Last month, someone improved their cholesterol numbers by 93 points by eating that way.)
Assume there are 3,500 calories in 1 pound of body fat.
Then cut, say, 300 calories daily out of your diet for, say, 3 years.
That's 109,500 calories a year or 328,500 calories over 3 years.
328,500 calories divided by 3,500 calories/pound is 93 pounds.
The math isn't that straight forward, but many people use the very math to explain weight loss, at least in the short term. I just can't buy into the math that 'calories in' equals 'calories out'.
That said, I've done the 30-day challenge three times, not restricted my caloric intake, and still lost weight (lost fat quicker than I gained muscle mass). So, even in the short-term, you can lose weight without restricting calories.
* Cutting carbs typically means people end up eating less calories*
Mostly true, but ore specifically, cutting carbs means that you are sending less sugar into your body. Less sugar means it is more difficult for the body to produce fat. Fat is more dense than muscle and the reason most people diet is to lose the fat.
I am not sure this is scientifically accurate, but this is how I make sense of it:
When I eat Paleo, my body thinks it is surround by high quality energy sources. It gets fed those energy sources frequently. The body recognizes that there is low risk that it will go a short period of time without high quality energy. It determines that it has little use for the fat it has stored on the body. The body then converts the fat into energy. Your body enters into a phase where you go for weeks (or months) of high energy because of all the fat you are burning by eating a lot of high quality food---food a caveman would eat.
I mentioned I kept track of all the food I ate in June 2012, and even after increasing my calories after going on low-carb, I still lost weight. What part of that did you not understand?
Just curious, but what makes real time so important to you? What do you do with your data instantly that wouldn't be better served rolling up over a longer period of time to remove any noise-iness and natural variability in your data? I'm genuinely interested in your use case.
I've also heard that KISSMetrics is more about identifying people rather than data points, so it makes retention and user-based events easier, but it seems mixpanel does that too, so I'm not sure.
I built the first version of Boxcar (http://boxcar.io) in a weekend -- because I was bored. Started on a Friday, submitted to Apple the following Sunday evening.
Since then we've grown to 1M+ users and have delivered 2B+ push notifications. We're a team of 4 now.
For mobile apps, your tools are basically decided for you already. Eclipse for Android, Xcode for iOS. The goal of an MVP is to keep things as stupidly simple as possible. Use external APIs if they already exist, use services like Parse, etc, to give you a leg up.
MVP is less about code and more about results. If you can get away with no coding at all, that's the ideal situation. :-)
Seems to be an impressive app.
So, when you say a weekend, you got that MVP from inception to live app? Normally, ideas are spontaneous and it will take some time to get the right feel of it.
So how did that happen with your boxcar?
Yes, you are right for the basic tools like Eclipse and XCode. But to integrate different product apis, like Parse/Nodejs it would already need a groundup knowledge to use them in your app. This is where I am lagging behind. I want to know how do you manage these kind of situations.
I belive this process is more of a progressive manner than a complete solution at one go.
Sincerely, it would really inspire me to read such kind of posts here and believe I am way too far from the fellow hn'ers.
Nice advice! One finds 2 paths I guess- to focus on the medium (code, framework, etc) or on the results for a MVP.. once the MVP gets enough traction, then even rewriting the whole app is not bad as long as we know the idea has potential.
As someone that has traveled from Kansas for many years for conferences, it's wonderful to see friends from the coasts coming to Kansas!