3 ms·
> This reminds me a SV company I worked for a couple years ago. The EM was always going on about impact. I was a staff engineer, needed to have organizational-l
by nine_zeros 3y ago
> This reminds me a SV company I worked for a couple years ago. The EM was always going on about impact. I was a staff engineer, needed to have organizational-level impact with my project... on and on. Meanwhile, I'd get so many interruptions for code reviews, meetings, etc. it was almost impossible to get any actual work done.
Been there. The obsession with levels and career ladder documents is too much sometimes. It is so hard to be an IC with constant org-wide impact as opposed to being a manager whose impact is automatically wider due to reporting structure.
- icedchai 3y agoI eventually left. I hated the culture. They would literally shame people for not hitting 90% of their sprint goals, meanwhile the interruptions were constant and never ending. Also, despite all the time spent on code reviews, the code base was incredibly difficult to work with. Technical debt did not begin to describe it. 5000 line single file "modules", decade old dependencies nobody dared upgrade, not to mention Python 2.7 (in 2022), multiple ORMs, on and on.