This is the most important comment in this thread here. It's not possible to start up a successful company when you're also on the brink of suicide, malnourished, and you're having deep internal conflict. Your startup is going to push those things on you by itself and adding to your personal conflicts and problems is asking for trouble.
I used Test::Unit for a long time, but I found it to be a poor tool when doing integration tests. RSpec lets me do both within the same DSL quite easily. That's probably why a lot of people flock to RSpec. I still have old Test::Unit code sitting in my RSpec suite that I haven't moved over to RSpec's DSL.
That being said, to a developer writing tests and doing TDD, Cucumber is a speed bump that doesn't need to be there. RSpec is great without lumping more crap on top of it.
Exactly. They could have also demanded that the series B does not take place. And they did neither of these things. Which most likely means the people that made the decision did not have the best interests of the company in mind.
It is not that complicated. Let's say there is X amount of economic benefit from the deal. Initially (i.e. before the series B) that benefit would be shared between Facebook and the initial (i.e., before the series B) shareholders of instagram. Facebook would get the benefit of owning the company minus the purchase price and the investors would get the purchase price.
But after the series B there is another party, the new Instagram shareholders which must also share in that benefit. This means that either Facebook or the initial shareholders or both get less benefit than they would have gotten if the series B had not happened.
So who got less benefit? Well in these cases one just has to ask oneself who is likely to make a decision against their own benefit. And when you look at people making decisions against their own benefit it usually the ones with the longest and remotest chain of fiduciary duties that do it.
So I guessed that it was facebook that might have done it because it has much more and more remote shareholders, so it is more likely someone may have slipped up on their fiduciary duties.
But I do not know for sure. It could have been the instagram owners or old shareholders that got screwed. In any event, it is quite certain that one or both of them did get screwed.
Another important point to consider is that Facebook has a pending IPO. It's very possible that they would have delayed or aborted the acquisition for some unknown reason related to the IPO. If that did happen, Instagram had the cash to keep running.
RackSpace has a fairly sane API for building new servers. If you're not adverse to using Ruby, the fog gem is pretty awesome when building servers for Amazon and Rackspace's Cloud.
I use Roll Out or Push It as my main deploy songs as well, but it doesn't get far into the song before the deploy is done. Once in a while, I throw Muhna Muhna into the mix.
I changed my co-worker's song to Rick Astley's Never Gonna Give You Up nearly a year ago when he was AFK. He hasn't changed it because now every time he deploys code, I get to listen to that damn song.
I don't even use Jenkins... we have our test suite and autotest running while we code. Instantly know when you're done breaking stuff and ready to deploy.
A CI server would be nice as a pre-deploy sanity check, but that requires me to push to it in order to get feedback.
I never really had any issues with Time Machine snapshotting when I don't have my external drive attached. It's worked pretty well for me.
I had a lot of problems when I first installed Lion, but I also had a lot of crap installed on my machine. I did a fresh install of Lion and everything is great. I don't have any of the problems described in the article and I didn't really have many to begin with.
Comparing Vista with Lion is dumb and the article reads as though the author knows it but decided to stick with the idea so that they could get some traffic for their dumb article title.
People had similar complaints about Rails and now it's pretty modular and flexible with what you include/exclude. A proposal for RVM to be more modular with what it does to your shell would have probably been well received.
