Joachim Rekt believes writing code is a non-negotiable daily practice for anyone with "engineer" in their title. This keeps skills sharp, ensures continuous growth, and is the most fundamental way to contribute, contrary to the common advice for senior engineers to delegate more.
Z.AI's culture mandates that technical leaders, including the founder, remain hands-on practitioners. The AI field evolves too quickly for a delegated, hands-off management style to be effective. Leaders must personally run experiments and engage with research to make sound, timely decisions.
Contrary to conventional wisdom, a distinguished engineer advises senior engineers to delegate the most challenging, interesting work. They should instead take on necessary but unglamorous tasks, which builds immense credit and allows junior engineers to grow faster on high-impact problems.
When senior engineers move away from hands-on coding, their understanding of the system becomes abstract. This leads to designs disconnected from reality, and they lose the trust of their team, who see them as out-of-touch architects without "skin in the game."
AI's productivity gains mean that on a lean, early-stage team, there is little room for purely specialized roles. According to founder Drew Wilson, every team member, including designers, must be able to contribute directly to the codebase. The traditional "design artifact" workflow is too slow.
The process of struggling with and solving hard problems is what builds engineering skill. Constantly available AI assistants act like a "slot machine for answers," removing this productive struggle. This encourages "vibe coding" and may prevent engineers from developing deep problem-solving expertise.
To bypass subjective debates and gain influence, junior engineers can build prototypes for all competing technical approaches. By presenting concrete, comparative evidence after hours, they demonstrate immense value and can quickly establish themselves as technical authorities, accelerating their path to leadership.
The role of a senior developer is evolving. They now focus on defining outcomes by writing tests that a piece of code must accomplish. The AI then generates the actual implementation, allowing small teams to build complex systems in a fraction of the traditional time.
Countering the "quality over quantity" mantra in software engineering, Robinhood's internal data reveals a positive correlation between the number of code lines contributed and the quality of that code. This suggests that top-performing engineers excel in both volume and craftsmanship.
To stay current in a fast-moving field like AI, passive learning through articles and videos is insufficient. The key is active engagement: experimenting with new platforms, trying new features as they launch, and even building small applications to truly understand their capabilities and limitations.
A critical cultural lesson from Facebook is that all engineering leaders must remain hands-on. Seeing a VP fix bugs in bootcamp demonstrates that staying technical is essential for making credible, detail-driven strategic decisions and avoiding ivory-tower management.