600K Lines, 60 Days: The Method Is Now Open Source

Key Takeaways

• 600k lines written in 60 days by YC CEO
• 35% of code comprised of automated tests
• Daily output peaks at 10k‑20k usable lines
• Open‑source tool gstack codifies his workflow
• Contribution count rose from 772 (2013) to 1,237 (2026)

Summary

Y Combinator President and CEO Garry Tan wrote more than 600,000 lines of production code in just 60 days, with roughly 35% of those lines dedicated to automated tests. He achieved this while maintaining his full CEO workload, averaging 10,000‑20,000 usable lines per day across three active projects. The effort produced 362 commits and a net increase of about 115,000 lines in the last week alone. Tan has distilled his process into an open‑source tool called gstack, making the methodology publicly available.

Pulse Analysis

Garry Tan’s recent coding marathon challenges the conventional wisdom that senior executives must delegate all technical work. By producing over 600,000 lines of code in two months, he illustrates that disciplined processes and automation can unlock developer‑level productivity even for a CEO. This feat is not merely a vanity metric; 35% of the output consists of test code, suggesting a strong emphasis on quality and rapid feedback loops that many organizations struggle to achieve at scale.

The open‑source project gstack captures the tools and workflows that enabled Tan’s output. It automates routine tasks such as code scaffolding, dependency management, and continuous integration, allowing developers to focus on high‑impact features. By publishing the methodology, Tan invites the broader developer community to adopt a repeatable framework that could reduce cycle times and improve code health across startups and larger enterprises alike. Early adopters report faster onboarding and fewer merge conflicts, underscoring the practical benefits of codifying best‑practice habits.

Beyond the technical advantages, Tan’s example signals a cultural shift in the startup ecosystem. When a high‑profile leader publicly codes at this scale, it validates the notion that hands‑on engineering remains a strategic asset rather than a purely operational role. This could inspire more founders to stay technically engaged, fostering a wave of innovation driven by deeper product understanding. As gstack gains traction, it may become a standard component of the modern founder’s toolkit, blurring the line between executive decision‑making and code contribution.