What happens after Yahoo acquires you
37signals.com
What happens after Yahoo acquires you
1–10 of 155 posts
Re: What happens after Yahoo acquires you
#2Re: What happens after Yahoo acquires you
#3Re: What happens after Yahoo acquires you
#4Reminds me of Brew Masters when the owner of Dogfish Head, Sam Calagione, mentioned that he had an offer to sell off his company for a nice amount but in the end he would still obsess about the fate of his company, and the name he built up for it, that it wasnt worth selling.
Re: What happens after Yahoo acquires you
#5These anecdotes will sound familiar to many people who have been through an acquisition. Acquisitions are not something any company is naturally good at, and they inherently threaten the bureaucracy of the acquirer. Despite good intentions, the corporate immune system usually kills off the interloper before it becomes established. Not to mention that the founders and best employees usually bail within a couple of years.
Re: What happens after Yahoo acquires you
#6Is it something every acquired company has to go through? Is there a right way to do this?
Re: What happens after Yahoo acquires you
#7Do we just keep being regular companies? Is there an alternative? How do we build things that matter (and require outside investment) and end in real change instead of just getting rich?
Re: What happens after Yahoo acquires you
#8Re: What happens after Yahoo acquires you
#9This article is mistitled. It should read 'What happens after anyone acquires you'. These anecdotes will sound familiar to many people who have been through an acquisition. Acquisitions are not something any company is naturally good at, and they inherently threaten the bureaucracy of the acquirer. Despite good intentions, the corporate immune system usually kills off the interloper before it becomes established. Not…
As hackers we tend to focus a lot on technical scalability issues. We love to work on things like NoSQL, the CAP-theroem, large scale caching and whatnot. But I think that the organization often becomes the bottleneck quicker than the web site. This is especially true now when we have services like Amazon AWS and GAE which helps us with the technical scalability issues.
So next time you work on that really cool memory optimization maybe you should ask yourself if you don't get better scalability as a whole if you focus your limited programming resources on features instead (so you don't have to hire that extra programmer to do that for you, since you work on your memory optimization).