tl;dr:"A deep dive with five Technical Program Managers (TPM) on what the role is, how it evolved, and how engineers and managers can benefit from working with TPMs." Gergely concludes that senior engineer already do lots of the things that TPMs do full-time. (2) Fast-growing tech companies rely heavily on TPMs to scale engineering efficiency. (3) The TPM role is spreading steadily across the industry.
tl;dr:This post covers: (1) The importance of writing for software engineers, engineering managers, and executives. (2) The process of writing well. Editing approaches to make your writing crisper and getting feedback on your writing. (3) Improving how you write. Observing and copying great writing. Habits to build your writing muscle. Continuous learning: courses, books, and tools to boost your writing.
tl;dr:95 recommendations divided by genres such as engineering management, engineering leadership & org design, software engineering careers, leadership and business, and others.
tl;dr:"Stories from 6 engineering leaders who succeeded in building and growing diverse teams," with the following key takeaways: (1) Underrepresented leaders make a difference. (2) There are tactical wins you can start now e.g. bias training, partnering with organizations. (3) Use structure to drive diversity outcomes & create processes around those outcomes. (4) Tactics need a defined strategy and goals.
tl;dr:Gergely looks at 30+ compensation related data points to see how companies, across different regions, are adjusting to the rapidly changing hiring market. His advice: "if your company has not yet made off-cycle compensation changes, you’ll likely have to make a case for a larger than usual raise for the new year. Start engaging your leadership now."
tl;dr:This post covers: (1) Common incident handling practices across the industry. (2) Incident review best practices. (3) Incident review practices of tomorrow. (4) What tech can learn from incident handling in other industries. (5) Incident review/postmortem examples and templates.
tl;dr:"12 questions to get a sense of what a tech company is like to work at, based on things most job postings do not mention:" (1) Are code reviews and testing both part of the everyday development process? (2) Do you follow an internal open-source model, where any engineer can access and contribute to most other codebases - with appropriate code ownership in place?
tl;dr:Gergely covers: (1) various project management approaches based on a survey of 100 companies. (2) Setup and processes of project management in big tech. (3) Why big tech don't use scrum. (4) A POV on how to run projects in your team.
tl;dr:More emphasis on total comp packages, seeing some companies move to one-year stock grants. Job seekers should optimize for happiness, identifying their "must-haves," and also have the opportunity to negotiate v hard. Employees can negotiate with current employers to improve their situation. Gergely also outlines how this is impacting more junior tech workers too.
tl;dr:"I’m a senior engineer, and I received a below-senior offer at a larger tech company. The pay is better, but I feel it’s unfair I don’t have the senior title I’ve already earned. What can I do?" Gergely guides us through the reasons for down-leveling, how to handle it when switching jobs and how to get ahead as a manager.