Earlier quoted context omitted.
> I don’t know which business school teaches people to say “ah can you smell that fresh mountain air” while they have their hands wrapped tightly around your neck … It’s all of them and the higher you get into management the more apparent it is. They sell a system of meritocracy where those who work the hardest get the rewards. Then you get into management and working side by side with people whose first job out of c…
> 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.
Watching an acquirer ruin your company
291–300 of 347 posts
Re: Watching an acquirer ruin your company
#292Earlier quoted context omitted.
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 and maybe not getting corralled into working ticket after ticket and sprint after sprint...endlessly. I have had numerous jobs in IT, and software development is by far the worst. Ticket grinding bullshit. The sad part is that developers think this is how software development is so they can't even demand better. Clueless.
Re: Watching an acquirer ruin your company
#293> 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…
In general it blows my mind that people don’t understand that: 1) losing a critical mass of developers is the beginning of a death spiral 2) the critical mass is smaller than you think 3) you lose the developer months before you know you’ve lost the developer
Re: Watching an acquirer ruin your company
#294Earlier quoted context omitted.
You get used to it. After a while if you become good at interviewing and going through the motions you are probably more secure than someone who has "job security", no matter how hard it is to fire someone a company can still go bankrupt. If I got fired tomorrow it would result in a vacation, probably followed by a raise. When you get to that place it isn't scary at all.
I'm guessing you are American and under 35 because there's a whole generation of you that considers an 13-year tech bull run with massive stock appreciation as normal, and the hardest problem is passing leetcode interviews. It's a very different story looking for a job in a real downturn like 2000 or 2008.
Re: Watching an acquirer ruin your company
#295Earlier 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 don’t think you understand what unions are for also, for every engineer, there is one who will claim to be able to do the job cheaper. that is why we need unions. that, and to get rid of leetcode. people already went to college and that should be enough.
I don't like or do LC interviews, but even if (a big IF) college prepared you for programming, a LOT of professionals don't study development or even attend college. How would they get into the industry? Take 2 years off later in life and attend college?
Re: Watching an acquirer ruin your company
#296Earlier quoted context omitted.
I wasn’t clear. Pilots absolutely have strong unions (which is partly responsible for their levels of pay). I was contesting that pilots are paid more than developers. If you have data that supports that, please share. It seems like an absurd claim.
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…
Re: Watching an acquirer ruin your company
#297Earlier quoted context omitted.
I'm guessing you are American and under 35 because there's a whole generation of you that considers an 13-year tech bull run with massive stock appreciation as normal, and the hardest problem is passing leetcode interviews. It's a very different story looking for a job in a real downturn like 2000 or 2008.
If you keep looking for the same job as you get older, yes. I'm well above your age guess and starting a new job soon, but it's definitely not the same role or expectations as 20 years ago. I've found that if you work to differentiate yourself as an individual the substitution cost is very high, so you can find work even in the most challenging environments. I think this would be a much harder strategy in a heavily u…
Re: Watching an acquirer ruin your company
#298Earlier quoted context omitted.
You get used to it. After a while if you become good at interviewing and going through the motions you are probably more secure than someone who has "job security", no matter how hard it is to fire someone a company can still go bankrupt. If I got fired tomorrow it would result in a vacation, probably followed by a raise. When you get to that place it isn't scary at all.
I'm guessing you are American and under 35 because there's a whole generation of you that considers an 13-year tech bull run with massive stock appreciation as normal, and the hardest problem is passing leetcode interviews. It's a very different story looking for a job in a real downturn like 2000 or 2008.
Re: Watching an acquirer ruin your company
#299Earlier quoted context omitted.
i don’t think you understand what unions are for also, for every engineer, there is one who will claim to be able to do the job cheaper. that is why we need unions. that, and to get rid of leetcode. people already went to college and that should be enough.
>> that, on to get rid of leetcode. people already went to college and that should be enough. I don't like or do LC interviews, but even if (a big IF) college prepared you for programming, a LOT of professionals don't study development or even attend college. How would they get into the industry? Take 2 years off later in life and attend college?
any good college will require significant programming work, so by the time you graduate 4 years later you not only have CS theory subjects down but are able to write software and can pick up any language in a few days.
Re: Watching an acquirer ruin your company
#300Earlier quoted context omitted.
I wonder whether there has ever been an attempt to calculate the loss-in-value caused by acquisition-as-shutdown-mechanism. They probably frequently lead to competitive benefits (and increased market share / revenue) for the acquirer, but the discontinuation of products presumably leads to lost time, effort, and potentially money as the former customers of the product look for alternatives (in a diminished market). I…
> 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…
> Have you seen this work in practice, do you have any examples to share?