Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



As a current employee, there's things I don't like, but the infrastructure is more custom than bad (far better than my last job)


Custom 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.


The 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.


^ it’s not an azure issue but a LinkedIn issue.


Didn't LinkedIn create Kafka? Was that some of the overengineering?


Kafka was made 15 years ago.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: