@ptr Also, this wasn't even the only product safety feature that got blocked (no pun intended) in the name of simplicity! It took forever and a day to ship the "people you follow" filter in mentions because of similar fears over complexity/aesthetics of adding a new tab.
@ptr lol sorry for leaving you with that shit sandwich (although I'll take a little credit for at least advocating for product safety to be a proper team). The block v2 saga was def the most eventful last 24 hours at any company I've worked at, that's for sure.
@shreyas 1) if employed, look for ways to broaden your skills - take on projects in a different product area, dive into budget/revenue models, etc.
2) even if you're not actively looking, build network, whether through events, PM communities, taking convos from founders/ recruiters etc
@mherdeg It's really only a matter of time. Things will keep working fine until they won't, and then there won't be the expertise around to bring things back up.
This is absolutely wild. If true, there will be less employees on Monday than when I joined a literal DECADE ago, with <1/2 the current users (not to mention the increased feature/tech debt/complexity over 10 years).
Despite the bad times, I remain grateful for my time there, and especially for all of the wonderful, talented, kind Tweeps I met. Whether you left a decade ago or today, I hope you're proud of the work you did, we did, in building this place. I know I am. Take care π
A quick nostalgia thread since it's only a matter of time before this site fail whales one last time, and no one is there to save it. God knows I'm not going to post this shit on LinkedIn.
The ugly: Getting poor performance reviews for "failing to build a relationship" with an EM who was later fired for incompetence & lying about data. Being told the "well had been poisoned" by an exec when trying to switch roles, despite my old & new managers being supportive.
@Carnage4Life Yeah, that whole thread is a weird (maybe deliberate) conflation of two things: (a) poor communication/rationale from eng on the specific tech debt needs/priorities, and (b) eng "owning" tech debt by default, and only expecting PM to care once eng has sufficiently rationalized