The best Hacker News stories from All from the past day
Latest posts:
How to draw S-curved arrows between boxes
How to draw S-curved arrows between boxes
South Africa’s omicron coronavirus outbreak subsides as fast as it grew
Germany is closing half of its reactors before the end of the year
Buying Influence: How China manipulates Facebook and Twitter
Tinder just permabanned me or the problem with big tech
Regulators Shut Down Lending Platform (YC Alum) LendUp
Regulators Shut Down Lending Platform (YC Alum) LendUp
Tell HN: AWS appears to be down again
Console is flickering between "website is unavailable" and being up for my team. This is happening very frequently just now, reliability seems to have taken a hit.
Zig 0.9.0
Omicron variant was 73% of U.S. covid cases last week
The Belgian government has removed ‘backdoor requirement’ from new law
Kodi: An Open Source Home Theater System
All Bitcoin private keys are on this website
Hidden Networks in TP-Link Routers
Hidden Networks in TP-Link Routers
Ask HN: Startup acquired by a large company and it sucks. What to do?
I work at a startup with ~50 employees (and have always worked at startups). Love the work and the people. Recently we were acquired by $LARGE_CORPORATION and the experience has been a living hell for all of us. Things that should take a few days take a few weeks. Things that should take a few weeks take a few quarters. It's slowly driving me insane.<p>The experience is best shared as a story.<p>I'm working on migrating our apps to the parent company's VM launching and deploy platform. Should be fairly straightforward, I think. Unfortunately, the deploy tooling isn't entirely compatible with our app so I ask the team if they can implement $X feature to support our app.<p>The first engineer I talk to doesn't even attempt to answer my question but redirects me to their manager. Ok, that's odd, I think, but whatever.<p>Manager says sure, just fill out this feature request doc. It's a Google Docs template with 4 (!) pages of required documentation to just explain why I want this feature implemented. It asks for my team name, the motivation, why I can't solve the problem some other way, yada yada...ok, I guess it's good to document your work, so sure. I fill it out and submit it.<p>No response after two days. Then I get an automated email that their <i>skip</i> level manager has approved the work. Huh? This is followed by an email that the team's eng manager approved the work. Why do two layers of management need to approve work on something they have no knowledge about?<p>Finally, after many rounds of arguing about why this needs to be done in the first place (ahem: you told us to migrate to your platform, and it literally does not work for our app), they quote us a delivery timeline of <i>end of Q1 in 2022</i>.<p>At this point I am in absolute shock. This should take no more than a few days to implement.<p>So I reach out to the manager and ask what is going on. This is a simple task, I said. Why does it take an entire quarter for your team to deliver? He doesn't have an answer.<p>I tell him I'm happy to fix the issue myself, if they link me to the relevant codebase. "It shouldn't be too hard to dig in and submit a patch," I think to myself. He says he cannot give me access to the codebase for compliance reasons, and that only members of his team have R/W on that repo. What???<p>This is insane. And this entire time I was only alllowed to interact with managers and have not spoken to a single engineer about the actual technical details. It is impossible to get anything <i>done</i> here now.<p>Is this how it's like at all large companies? What should I do?
Show HN: Lisp with GC in 436 Bytes
Tesla remotely unlocks Model 3 car, uses smart summon to help repo agent
TinyVG: A challenger to the throne of vector graphics