Meta reviews

- Most of the codebase I've seen is messy and badly documented. It is difficult to find what you need and understand what you find. Making an impact requires equal parts software engineering and archeology. - There is *a lot* to learn w.r.t. internal processes and tools, much of which won't be transferable to other companies. They prepare you for some of it, but not most of it. - They have only recently begun to take automated testing seriously.

- Performance evaluations (PSCs): We talked about PSCs year-round, and it felt like every little thing I did (positive or negative) would show up on a PSC. Employees are technically assessed on many aspects of performance, but the only one my manager focused on was lines of code. - Competitive culture: Constantly talking about PSCs meant everyone on the team was afraid of any appearance that they did something wrong, which created a culture of blaming others and never admitting mistakes. Managers either stayed out of it or made it worse. - Workload: My tech lead set deadlines that were too aggressive and didn’t listen when my teammates and I pushed back, so we were constantly behind schedule. Working late at night and on the weekends consistently was required just to remain a few months behind schedule. - Asking for Help: Several members of my team had to ask for help writing code many times per day. Most of their questions could be quickly solved by typing a few words into a search bar and looking at the first result, but they still asked another engineer any time they encountered something they didn’t already know how to do. They would intentionally not ask managers and avoid asking for help while managers were within earshot.