As soon as someone hands you the check it's no longer "your" company and you should stop thinking of it as such. Only misery lies on that path. I see this on a smaller scale where ICs leave a company and take a copy of "their" code (ask Sergey Aleynikov [1] if that's a good idea). It's not yours. If you ever use it you could face legal consequences. And there's no code I've ever written that I wasn't convinced I coul…
Have you ever started a business before? Yes, you technically no longer own it once sold, but there's a huge amount of blood, sweat and tears that goes into building something from nothing - not to mention a sense of loyalty to your staff - and you genuinely do want to see it go into good hands and become managed well. I guess a somewhat leaky analogy would be like giving away a dog you raised to another family and f…
Watching an acquirer ruin your company
191–200 of 347 posts
Re: Watching an acquirer ruin your company
#192> As soon as Sphero completed the acquisition, bringing Kelsus in as an app developer, two things happened: 1) Sphero told us they needed fully revamped iOS and Android apps six months later with no schedule wiggle room. 2) Sphero spent the first two of those six months organizing a team on their side and hashing out requirements for the new apps. This exact pattern has preceded every mismanagement disaster I've ever…
The story fills in all the reasons why ‘management’ start at #1. Company A buys company B for a product it believes in. Company A knows that company B was incapable of getting product to finish line, which is why they sold out. No problem though, company A has done this before… The managers at company A are assigned to ship product, just like they have before. Managers can’t say “its all good, we’ll give them a coupl…
I think this hits the nail on the head.
A bunch of reasonably competent people went in with the best intentions, all in good faith and over time it became clear certain assumptions were either too optimistic or simply wrong.
While there is definitely blame to be apportioned, the frustration felt by all involved leads to a very human reaction of calling it malevolence or incompetence.
Re: Watching an acquirer ruin your company
#193Earlier quoted context omitted.
And still too busy smelling our own farts to unionize.
Well, question is which part of the world you live in, of course. But I don't need to unionize. If I am not satisfied in my job I can switch. Each consecutive job hop past 15 years got me better pay, better benefits and sometimes a better job (sometimes it was equaly shitty as the prevous one but for better money). This does not happen for unionized workers. Maybe in the future we will have to unionize. Definitely no…
Right now management will be off-guard, not expecting any unionisation push and will be a little bit unprepared as to how to counter it (that is, if they even try). Employees will likely feel comfortable openly discussing unions knowing that they probably won't feel any reprisals (and if they do, well the job market is still pretty good for the moment). The tough part would be convincing someone on $1x0,000/year that they might benefit from a union.
Re: Watching an acquirer ruin your company
#194All too familiar a story, and the advice at the end ("know your acquirer") is pointless. Simply put, the acquirer isn't ruining your company, they are ruining their company. The contract you signed and the money you exchanged gives them that right. It is foolish to expect that you will get a big payday and will get to keep setting the company direction and calling the shots as you like indefinitely. Here's better adv…
Agree. It's impossible to really know your acquirer unless they are a bigger publicly traded company. Every acquirer puts their best foot forward, talks about how awesome their culture is, and how they are going to do all the things to help you grow faster. IME, it never works that way.
> the moment you sign the contract start counting the days left in your retention agreement and quit right after.
That's a bit too cynical for me. But, you do need to answer some questions, do you want to be an employee? Are you ok not being the one in charge? If you got a decent payout in the acquisition, you have a lot of freedom in the new job if you want to try to keep things going.
One other thing to note, is that many times companies can be spun back out. I know multiple founders who have had this happen.
Re: Watching an acquirer ruin your company
#195As soon as someone hands you the check it's no longer "your" company and you should stop thinking of it as such. Only misery lies on that path. I see this on a smaller scale where ICs leave a company and take a copy of "their" code (ask Sergey Aleynikov [1] if that's a good idea). It's not yours. If you ever use it you could face legal consequences. And there's no code I've ever written that I wasn't convinced I coul…
Re: Watching an acquirer ruin your company
#196Possibly more common is when the company is bought specifically to shut it down, because the product's success would hurt, or is hurting, sales of their own product. There used to be a category of software called "electronic design automation". It presented an interactive editor where you could enter the schematic diagram of an integrated circuit, and also enter a chip layout, and it would ensure that they matched. I…
I design semiconductors and I use EDA software everyday.
I know Cadence was formed from a merger in 1988 and they have since bought around 30 other EDA companies.
Re: Watching an acquirer ruin your company
#197Earlier quoted context omitted.
This is something I've come across in my own experience. If you don't actually have any experience in the problem space, the best thing you can do is make something that just barely works, then scrap it. Then all the unknown unknowns become known unknowns and you can actually create good solutions to it. All planning is a waste if you don't even know where the speed humps will lie.
It's basically a variation of Chesterton's fence[1]. There's a lot of hubris in thinking one could write a piece of code better than someone else if one has never attempted to write that piece of code, especially when never even having done anything like it at all. [1] https://en.wikipedia.org/wiki/Chesterton%27s_fence#Chesterto...
Re: Watching an acquirer ruin your company
#198Earlier quoted context omitted.
Well, question is which part of the world you live in, of course. But I don't need to unionize. If I am not satisfied in my job I can switch. Each consecutive job hop past 15 years got me better pay, better benefits and sometimes a better job (sometimes it was equaly shitty as the prevous one but for better money). This does not happen for unionized workers. Maybe in the future we will have to unionize. Definitely no…
I also don’t need to unionize but I’m pro-union. I think software should have a guild like the actors guild, that enforced minimum standards. when Kickstarter ran its unionizing campaign it turns out one of their demands was no productivity tracking software! I would love to know as a member of such a hypothetical guild I have collective clout to ensure I’ll never have to deal with a bullshit metric tracker again.
This is naive. Any ticket tracking system can be used to track productivity. And if you don’t have a ticket tracking system to organize work, that’s a miserable environment to work in.
Re: Watching an acquirer ruin your company
#199Earlier quoted context omitted.
Well, question is which part of the world you live in, of course. But I don't need to unionize. If I am not satisfied in my job I can switch. Each consecutive job hop past 15 years got me better pay, better benefits and sometimes a better job (sometimes it was equaly shitty as the prevous one but for better money). This does not happen for unionized workers. Maybe in the future we will have to unionize. Definitely no…
> And this is not a matter of pay, e.g. airline pilots are paid more than programmers here yet they are heavily unionized. [Citation needed]
https://fr.glassdoor.be/Salaries/airfrance-pilot-salary-SRCH...
https://www.payscale.com/research/FR/Job=Software_Engineer_%...
Re: Watching an acquirer ruin your company
#200Earlier quoted context omitted.
Well, question is which part of the world you live in, of course. But I don't need to unionize. If I am not satisfied in my job I can switch. Each consecutive job hop past 15 years got me better pay, better benefits and sometimes a better job (sometimes it was equaly shitty as the prevous one but for better money). This does not happen for unionized workers. Maybe in the future we will have to unionize. Definitely no…
>But I don't need to unionize. If I am not satisfied in my job I can switch. [...] This does not happen for unionized workers. I can't work out what "this" is that does not happen to unionised workers? Unionised workers can switch jobs to get more pay too.