Live data from Hacker News

Watching an acquirer ruin your company

startupwin.kelsus.com

221–230 of 347 posts

Re: Watching an acquirer ruin your company

#221
post #188

Earlier quoted context omitted.

> I am never allowing myself be held hostage. So, you navigate this quagmire begrudgingly, yet don't favour unionisation?

Unionization does not magically change poorly managed companies into well managed ones.

Of course it doesn't happen by magic, it takes dedication and hard work.

Re: Watching an acquirer ruin your company

#222

Earlier quoted context omitted.

Word to the wise: start looking for a new job when that clock starts ticking. You may decide to stay but great to have something else to parachute into as an option. Second thing: you can change jobs as often as you want. I am for loyalty but you can’t know what a job will be like until you work it.

This may be good advise, but I hate it. Personally, I couldn't put my heart into the job hunt, while at the same time giving my best at the current job. In other words: just the step of starting to search for a job is for me synonymous to accepting defeat at the current job.

IMO nobody should "give their best" at a job they feel has enough red flags to warrant a search for a new one.

Re: Watching an acquirer ruin your company

#223
post #87
post #37

Earlier quoted context omitted.

Dealing with exactly 1 & 2 right now. #3 doesn't really apply in my case because 80% of the devs are budget staffing agency hires. But on that note, I'd add a 4th point: Management panics when they realize they won't make the self imposed deadline and start throwing bodies at the problem. In our case, we went from 2 teams to 8 over night. The very few engineers who actually were capable of shipping features became sw…

>8hr "planning" sessions One place I was at had quarterly 3 day planning sessions. That was something else.

I worked on one team that had a one week planning period every two weeks. The planning week, for us regular devs, was “do whatever you want” and it was epic. There were basically no bugs because a few of us liked tackling bugs for fun. Other people worked on optimization problems and code hygiene.

For the people doing planning, they were always busy playing ticket shuffle, asking random devs random questions all the time. But those two weeks was cray and anything not done by the end of the sprint had to be done by the end of the planning period, and you better have a good reason.

Re: Watching an acquirer ruin your company

#224

> 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…

That description sounds like a failure of C-Level at Company-A to do tgeir due diligence and properly allocate resources & schedule.

Then everyone pays for their mistakes, and the whole thing is a waste .

Optimism is essential in any endeavor, but it is no substitute for starting with accurate -in detail- assessments & provisioning of resources.

They (the Corp-A C-Levels) had one job here...

Re: Watching an acquirer ruin your company

#225

Earlier quoted context omitted.

My wife had a client that went on to play in the walking dead. In order for my wife to be able to continue to do her client’s hair, she had to join the actor’s guild and be “licensed” by them and pay dues. So, I’d say they (at least the actors guild) def can reduce your mobility, even say which hair stylists you are and aren’t allowed to use.

Well, in order to do her hair for the role . She obviously could style her hair for events in her private life, right? A wedding or whatever? It seems a stretch to say the union interfered with her 'mobility', any more than you can't do plumbing on a public building without having a license etc.

They have hairstylist on site for the role, as well as wigs. But even in her private life, she had to use guild sanctioned hair stylists.

Re: Watching an acquirer ruin your company

#226
post #68

Earlier quoted context omitted.

At google it was repeated that Sergey Brin used to say "all work is throwaway work, it's only the time horizon which is in question".

It's kind trite to say “much is explained”, but… that explains so much about google.

Throwing away code and throwing away products/features are completely different things, and only one of those is a real problem for end users.

Re: Watching an acquirer ruin your company

#227

Earlier quoted context omitted.

Well, in order to do her hair for the role . She obviously could style her hair for events in her private life, right? A wedding or whatever? It seems a stretch to say the union interfered with her 'mobility', any more than you can't do plumbing on a public building without having a license etc.

They have hairstylist on site for the role, as well as wigs. But even in her private life, she had to use guild sanctioned hair stylists.

I'd need a citation for that. Seems impossible to enforce, and a gross violation of privacy.

Re: Watching an acquirer ruin your company

#228
post #44

Possibly 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'm curious which companies you are talking about? 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. https://en.wikipedia.org/wiki/Cadence_Design_Systems

Back then the big EDA outfits were Mentor Graphics, Daisy, and Valid. ECAD became Cadence, embraced silicon compilers, and ate everybody's lunch.

Back then, chips were still laid out by pasting up prepared logic blocks, gates, and occasional custom transistors, and routing metal traces between them, all on what we would today call a low-resolution workstation monitor. A million transistors was a lot. These would be output via a plotter to make photomasks for the various doping, glass, and and metal layers.

The EDA software of the time, besides supporting manual editing editing of layouts and schematics, would simulate whole chips taking into account capacitance of wires and transistor inputs, propagation delay, and drive capability of output transistors. It would also apply geometric checks to make sure the layout conformed to rules of the target process. Where violated, somebody would need to redraw that bit, which might mean moving stuff out of the way.

Somebody would have to make up sequences of values to feed to inputs, and others to check outputs against.

So the period when MG was buying and shuttering silicon compiler startups was '85 to '89.

I think after Cadence won, Mentor Graphics got more involved in supporting embedded system design and firmware integration, leaving chips to others. Daisy merged with Cadnetix and went bust in 1990, and after twists and turns what was left became part of Mentor Graphics in 1999. Valid was folded into Cadence in 1991.

Cadence tried and failed to buy MG in 2008. MG was finally bought by Siemens AG in 2016.

Re: Watching an acquirer ruin your company

#229

Earlier quoted context omitted.

They have hairstylist on site for the role, as well as wigs. But even in her private life, she had to use guild sanctioned hair stylists.

I'd need a citation for that. Seems impossible to enforce, and a gross violation of privacy.

Contracts are amazing… and terrifying. Feel free to send them an email and ask.

Re: Watching an acquirer ruin your company

#230
post #195

Earlier quoted context omitted.

A child is still your child, even after they turn 18.

Are you implying your own your child. Because that’s a perfect analogy, once there 18 they are independent. It’s just like expressing regret for a sold company

“Own” is, for obvious reasons, not the word we use about children , but in practice it amounts to the same thing. A parent or guardian has complete control over what their child does and where it goes. Until the child turns 18. But we still call it “their” child.
Post reply on HN