Michael Bolin's experience at Google shows that working hard on high-quality but low-priority projects can lead to frustration and stalled career growth. True impact comes from finding the intersection of personal passion and company-wide strategic importance.
At Meta, Michael Bolin built the 'Buck' build system during a hackathon to solve excruciatingly slow Android iteration times. Despite widespread skepticism, the dramatic performance improvement won over doubters, proving that solving your own pain can create massive organizational value.
When building 'Buck' at Meta, Michael Bolin faced resistance from teams fearing deviation from standard tools. He successfully navigated this by framing the project as an Android-only solution, not a company-wide replacement. This reduced the perceived threat, allowing the project to gain traction before expanding.
The key to the 'Buck' build system's performance was understanding that the existing tool needlessly rebuilt everything. By introducing intelligent caching for unchanged components and simplifying modularization, the system avoided redundant work, leading to massive speed improvements for incremental builds.
Michael Bolin attempted to tackle Meta's massive 'web speed' problem, a 'hero quest' that didn't align with his strengths. This failure taught him that senior impact comes from choosing projects that leverage one's genuine skills and interests, not just tackling the biggest available problem.
To manage its enormous monorepo, Meta developed 'Eden,' a virtual file system. Instead of downloading all files, it only fetches them when an operation requires them. This decouples the performance of common developer actions, like switching branches, from the ever-increasing size of the repository, enabling scalability.
Michael Bolin correctly predicted a technical risk but his forceful communication created conflict, damaging relationships and delaying his promotion. The incident taught him that successful influence requires not just correct insights but also effective, empathetic communication.
Michael Bolin, a tech lead on OpenAI's Codex, says models now generate 80-90% of his code. He reserves manual coding for critical, low-level tasks like security sandboxing. For most work, including debugging and refactoring, he relies on the AI agent to maximize his throughput.
While local coding agents have product-market fit today, OpenAI's Michael Bolin argues the long-term trend is remote agents. To achieve true automation—like having an agent autonomously tackle every new bug ticket—workloads must run in the cloud, unconstrained by a developer's personal machine.
A surprising side effect of using AI at OpenAI is improved code review quality. Engineers now use AI to write pull request summaries, which are consistently more thorough and better at explaining the 'what' and 'why' of a change. This improved context helps human reviewers get up to speed faster.
To become a more versatile engineer, Michael Bolin suggests participating in Capture The Flag (CTF) events. These security-focused competitions are like a 'computer decathlon,' forcing you to learn diverse skills like assembly or reverse engineering that you wouldn't encounter in a typical day job.
Michael Bolin proposes a three-step algorithm for career impact: First, identify your genuine passions. Second, understand your employer's strategic priorities. Third, find the intersection between the two and dedicate yourself to it. This alignment maximizes your success and avoids wasted effort.