4 ms·
As someone who worked at LI. They spent years and god knows how many millions TRYING to move to Azure with the Blueshift project..before pulling the plug. They
by hasty_pudding 3y ago
As someone who worked at LI.
They spent years and god knows how many millions TRYING to move to Azure with the Blueshift project..before pulling the plug. They hired armies of contractors.
They didn't stop by choice.
They stopped because their tech stack is a giant over engineered unmovable turd.
- bbkane 3y agoAs a current employee, there's things I don't like, but the infrastructure is more custom than bad (far better than my last job)
- vasco 3y agoCustom is usually bad, just takes longer to reveal the problems. Sometimes companies need to create custom things, the mistake is continuing to invest in them when a community project appears and doubling down for years until nobody in your org knows how it's done "normally" and nobody that you hire knows anything about your stack.
- deleted 3y ago[deleted]
- hasty_pudding 3y agoThe entire company has no Q.A team. The amount of bugs I troubleshot in that tech stack was staggering just for basic day-to-day stuff. promotion based engineering means an engineer shits something out that looks cool in a demo then bails to the next cool demo project while the rest of us are stuck with the reality of the turd.
- bushbaba 3y ago^ it’s not an azure issue but a LinkedIn issue.
- carlivar 3y agoDidn't LinkedIn create Kafka? Was that some of the overengineering?
- hasty_pudding 3y ago[flagged]
- hasty_pudding 3y agoKafka was made 15 years ago.