Skip to main content
Steve Francia

Steve Francia

United States

There's a strange loop at the heart of Steve Francia's (@spf13) work: the CLI framework he built — Cobra — now powers GitHub CLI, the very interface through which millions of developers interact with GitHub itself. It also runs inside Kubernetes, Docker, Dropbox, and 150k+ other applications. Hugo powers 500k+ websites including letsencrypt.org, kubernetes.io, and brave.com. Viper runs throughout the Go ecosystem, powering over 100k libraries and applications. Hundreds of thousands of GitHub stars place him among the top 50 engineers on GitHub by project adoption. Steve has spent 30 years finding technologies about to matter and then doing the work to make sure they do. In high school, he was convinced he'd been born at the wrong time. The PC revolution had already happened. He had no idea the internet was about to reshape everything, or that he'd be in the middle of it. At MongoDB he pioneered the developer first database — a model the entire industry eventually followed — helping take it from obscurity to #4 globally. At Google, he led Go growing it from 400 k to 4.5 million developers and co-founding the Open Source Strategy team. At Docker, he helped establish OCI and CNCF, turning containers from a clever idea into foundational infrastructure. At Two Sigma, he brought that same developer-first thinking to quantitative finance, leading AI/ML platform strategy for one of the world's most sophisticated algorithmic trading firms. He has spent as much time building the spaces developers gather as building the tools they use: organizing and keynoting 40+ international conferences, serving on the Drupal Association board, writing the open source guidelines now used across 5,000+ Google projects. Google Developer Expert. O'Reilly author. Philosophy degree, which turns out to be surprisingly useful for thinking about how technology and the human stack should work. Father of four. Skateboarder at heart. Always curious. Writing at spf13.com.

Community Contributions

The 9 Cost Factors

This is the second entry in the True Cost of a Language series. Language choice is among the most expensive strategic decisions a technical leader will make, and many CTOs choose to delegate it. Every technical leader knows the pain: your team is debating languages, everyone has data, much of it conflicts, and somehow a decision that will determine 40-60% of your development costs is being made based on whoever argues most passionately. There’s a reason these conversations feel broken. We’re having the wrong conversation entirely. We debate technical features when we should be evaluating economic impact. We argue about what languages can do when we should be measuring what they will cost.

Blogpost / 11-11-2025

Why Engineers Can't Be Rational About Programming Languages

In his insightful blog post, "Why Engineers Can't Be Rational About Programming Languages," Steve Francia explores the hidden drivers behind one of the most expensive choices a tech company can make: selecting a programming language. Drawing on his extensive leadership experience at companies like Google, MongoDB, and Docker, Francia argues that language debates are rarely about pure technology. Instead, they are deeply rooted in identity, emotion, and ego. He introduces the concept of the "visible" versus "invisible" conversation. While engineers publicly debate technical merits like memory safety or compile times (the visible conversation), they are often subconsciously defending their personal brand and professional identity (the invisible conversation). Highlighting fascinating neuroscience research, he explains that challenging these identity-based beliefs triggers a biological threat response in the brain, making objective evaluation nearly impossible. This subconscious bias routinely leads to massive technical debt, delayed product launches, and skyrocketed burn rates, as companies unknowingly foot the bill for an engineer's sense of self. Ultimately, Francia argues that we must stop treating language selection as a technical holy war and start viewing it as a critical economic decision. This thought-provoking piece serves as the introduction to his broader series on calculating the true, long-term costs of programming languages.

Blogpost / 11-03-2025

Related Stars