The Hardest Part of Management: Letting Go of Code
On the 'Manager's Path' podcast, first-time engineering managers from Google and Meta agreed on the biggest challenge of the role transition. The consensus was, “The hardest part is letting go of code, and learning that your wins are now through others’ growth and delivery.”
Letting go of code is a common struggle for new managers, who often fear losing technical skills or feel a sense of imposter syndrome. The transition requires a shift in mindset from being the primary problem-solver to empowering the team to find solutions. This means moving from a hands-on-keyboard role to one focused on mentorship, removing obstacles, and guiding the team's overall technical and social health. A key challenge is balancing technical leadership with people management. Technical leaders influence through their expertise in system design and architectural decisions, while people leaders focus on team development, performance, and well-being. Effective managers learn to blend both, using their technical background to inform strategic decisions while prioritizing the growth and success of their team members. For frontend engineers, the technical landscape continues to evolve rapidly. The new React Compiler, for example, automates performance optimizations by handling memoization at build time, reducing the need for manual hooks like `useMemo` and `useCallback`. This allows developers to write cleaner code focused on logic rather than optimization mechanics. At the same time, signals-based reactivity, popularized by frameworks like SolidJS and now adopted by Angular and Preact, offers an alternative to the virtual DOM. Signals provide a more direct way to track and update state, leading to fine-grained reactivity and potentially better performance in complex applications. WebAssembly (Wasm) is also becoming increasingly important for performance-critical frontend tasks. By compiling languages like Rust and C++ to a binary format that runs in the browser, developers can offload heavy computations like 3D rendering, video editing, and data processing from the main JavaScript thread, resulting in faster, more responsive applications. High-profile applications like Google Earth and Disney+ already leverage Wasm for enhanced browser functionality. AI is significantly reshaping frontend development workflows. AI-powered tools like GitHub Copilot and Tabnine automate repetitive tasks such as code completion and error detection, allowing developers to focus on more complex problem-solving. AI is also being used to generate UI designs from text prompts, automate accessibility checks, and provide real-time UX suggestions based on user data. For engineers building internal libraries, a strong focus on Developer Experience (DX) is crucial. This involves creating APIs that are consistent, predictable, and well-documented. Good DX reduces cognitive load, speeds up onboarding for other engineers, and ultimately leads to a more productive and less error-prone development environment. As teams scale, engineering leaders must adapt their strategies. This includes establishing clear hiring processes that prioritize both technical skills and cultural fit, implementing robust onboarding and mentorship programs, and using data-driven approaches to track team performance. Effective leaders at scale also focus on aligning engineering efforts with broader business goals through regular communication with product and other departments.
