Live data from Hacker News

Watching an acquirer ruin your company

startupwin.kelsus.com

301–310 of 347 posts

Re: Watching an acquirer ruin your company

#301
post #107

Earlier quoted context omitted.

> Software engineers have been tricked into thinking they are part of the in club because they are paid well enough to have the lifestyle that the middle class had between ww2 and the 80s This, and additionally we've been tricked into feeling guilty about it as well.

If you think thatthe lifestyle of a software developer with a few years of professional experience is only as good as the middle class between the late 40's and 80's you're either vastly revising history or weren't there. And before you trot out home ownership remember that all those tiny post-war bungalows housed families bigger than yours and were not located in the handful of big centers were housing is so expensi…

Most software developers do not work for faangs. 2xxk or above salaries are beyond imagining for most

Re: Watching an acquirer ruin your company

#302
post #10

I’ve seen this twice. First time the PE firm installed their CEO who came in and immediately started talking about cleaning house. A bunch of developers left fearing a layoff. That was bad enough, but what he really meant was sales. He gutted the sales team and brought in his guys. Sales tanked, company growth stopped, hard. Features dwindled and bugs grew. This clown and his cronies were gone after two years and the…

> Getting to see these type of disasters first hand is pretty cool imo.

I've literally just got to watch a company get ran into the ground by the new owners. Learnt a bunch and once the legal stuff is over I'll have an amazing blog post to write.

In a few sentences.

Tech Side: A company decides to rewrite an application in 3-months, it takes 18-months and couldn't even invoice all the customers upon release. Biz Side: The company has a "better" strategy created for it by people who don't understand the industry after all the original business people fleed and then starts having to do all the stuff the original people were doing.

Re: Watching an acquirer ruin your company

#303

Earlier quoted context omitted.

Well, depends on the country you live in. My country: https://www.platy.cz/platy/doprava-spedice-logistika/pilot https://www.platy.cz/platy/informacni-technologie/programato... Average is CZK per calendar month gross (which is some 25-30% higher than net). Pilots 38k - 132k Programmers 36k - 86k as employees. If you work as a freelancer programmer (i.e. you have your own trade license) you can easily earn twice as mu…

It's pretty disingenuous to equate a RyanAir pilot with a student, which speaks to the misleading nature of comparing these statistics straight up; go look at what it takes in terms of training, experience and seniority to get to one of those higher paid pilot jobs. Now compare it to software development. 36k is less than minimum wage in Canada ( < $2K CAD / month); junior developers are easily making 3x that in thei…

> It's pretty disingenuous to equate a RyanAir pilot with a student

Ironically, as Ryanair pays pilots significantly more than the range in the GP's comments (at below the low-end and high-end), including them would support their argument.

The only way to make the claim that pilots earn more than developers stick is to ignore all but the high-end of pilot salaries at major airlines and include all developers. A fairer comparison would either be to include all pilots (including the low end piston engine pilots at skydiving DZs and other utility roles) or to only include the top-earning professional developers (maybe MAGMA).

Re: Watching an acquirer ruin your company

#304
post #220

Earlier quoted context omitted.

A few years ago lots of companies would have assumed that someone doing too much "job hopping" was unloyal and probably not competent enough to stay for more than a year or so. Today it's so incredibly common (and hiring processes are extremely strict compared to before), that most companies see having started multiple jobs as "validation" from other companies.

In my experience, it still seems to correlate that candidates with a lot of job hopping also don't make it through the full set of technical interviews.

I believe you. I guess it depends on where they worked, and if the interviews there were strict.

Re: Watching an acquirer ruin your company

#305
post #283
post #193

Earlier quoted context omitted.

Would this not be the best time to form a union, though? If we start to hit tough times when programmers are treated like shit and the job market is tight, then your colleagues will be less inclined to rock the boat and management will be actively trying to crack down on any attempts to organize. Basically when you need a union it could be too late. Right now management will be off-guard, not expecting any unionisati…

Software engineers: "No, it's going to be different for us!" Education still doesn't prevent us from falling in particular traps.

Yep. Hell I'm guilty of the same thing. I'm saying "we" should unionise and it's a good thing to do - while not unionising myself. My defence (excuse!) is that I'm a foreigner, my local language skills suck to the point that I'd struggle to understand local employment law so I'd be a pretty awful person to spearhead this :)

Re: Watching an acquirer ruin your company

#306
post #192

Earlier quoted context omitted.

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…

> At every stage everyone is doing their job. Everyone is trying to do the right thing for success and to not get fired. Everyone has a problem that can only be fixed by someone at a different level compromising on their quality of work or their personal happiness. 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…

Assumptions being too optimistic or simply wrong, is a kind of incompetence though isn't it?

Re: Watching an acquirer ruin your company

#307
post #263

Earlier quoted context omitted.

> open source software can mitigate some of the risks Have you seen this work in practice, do you have any examples to share? It’s hard to take seriously at face value for two reasons: 1- generally speaking it might undermine the acquisition in the first place since acquirers and investors and boards tend to like private potentially patentable IP, or at the very least proprietary code. 2- More importantly using your…

> > open source software can mitigate some of the risks > Have you seen this work in practice, do you have any examples to share? Blender? https://en.wikipedia.org/wiki/Blender_(software)

Is that an example of an acquisition-as-shutdown? Or even an acquisition at all? Blender is a good example of an open source model working, and I don’t know the history, but the article implies that neither NeoGeo nor NaN closed due to acquisition, so Blender might not be an example of what we were talking about above, no?

Re: Watching an acquirer ruin your company

#308
post #270

I watched that happen from the inside during the "dotcom" bust, Not a startup, but we'd grown to be a public billion dollar revenue organization when we were acquired by a much larger company (not using names here, as I'm sure there are folks on HN who were also there and would remember this and I don't want to doxx myself). We were very profitable and had an excellent company culture, with almost everyone pulling in…

For a second there I thought you were talking about EDS. Wouldn't surprise me if it was some other HP acquisition though.

>For a second there I thought you were talking about EDS. Wouldn't surprise me if it was some other HP acquisition though.

No on both counts, but not bad guesses. :)

Re: Watching an acquirer ruin your company

#309

Earlier quoted context omitted.

> when Kickstarter ran its unionizing campaign it turns out one of their demands was no productivity tracking software! 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.

But it also means at minimum a middle manager can’t use software that does stupid shit like neatly displaying comparable lines of code and stack rank devs based off this. I like this minimum. I don’t need a union to perfectly solve the problem of micromanagement but I can happily pay portions of my salary towards minimum standards of workplace environment.

> But it also means at minimum a middle manager can’t use software that does stupid shit like neatly displaying comparable lines of code and stack rank devs based off this

A middle manager is not allowed to use git?

Re: Watching an acquirer ruin your company

#310
post #24
post #10

I’ve seen this twice. First time the PE firm installed their CEO who came in and immediately started talking about cleaning house. A bunch of developers left fearing a layoff. That was bad enough, but what he really meant was sales. He gutted the sales team and brought in his guys. Sales tanked, company growth stopped, hard. Features dwindled and bugs grew. This clown and his cronies were gone after two years and the…

Reminds me a a company I worked at, I can't say it's name, let's just say it rhymes with Dewlett Dackard. 1) Start with a $55 billion dollar company... 2) Hire a new CEO and cronies that are going to make miracles happen with with a very expensive acquisition of another company. 3) 18 months later the miracles have not happened. CEO and cronies are invited to leave with very generous golden parachutes. 4) Start with…

only $5b of value destruction isn't bad, considering the possible range of outcomes
Post reply on HN