Skip to content
0:00 / 0:00

#mitchellhashimoto#ghostty#hashicorp

Mitchell Hashimoto’s new way of writing code

The Pragmatic Engineer

543K subscribers • 6 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Mitchell Hashimoto, co-founder of HashiCorp

Beginner. No background in the topic needed.

345K views8 months ago1 recommendation

Tools and practiceCareers and interviewsThe tech industryTransformers and LLMsOpen source

Mitchell Hashimoto discusses his AI-assisted coding workflow, the history of HashiCorp, building Ghostty, and managing open-source contributions in the AI era.

How has the day-to-day workflow of Mitchell Hashimoto changed, thanks to AI tools? Mitchell Hashimoto is one of the most influential infrastructure engineers of our time, and is one of the most pragmatic builders I’ve met. He is the co-founder of HashiCorp and creator of Ghostty. In this episode, we talk about how he got into software engineering, the history of HashiCorp, and the challenges of turning widely used open-source tools into a durable business. We also go into what it’s really like to work with AWS, Azure and GCP as a startup. Mitchell shares how he uses AI these days, and how agents have completely changed how he works. We touch on Ghostty, open source, and what’s changing for software engineers and founders in an AI-native era. If you're looking for brief takeaways, see 9 of my main ones here: newsletter.pragmaticengineer.com/p/mitchell-hashimoto — *Brought to you by our season partners:* • Statsig — ⁠ The unified platform for flags, analytics, experiments, and more. statsig.com/pragmatic • Sonar – The makers of SonarQube, the industry standard for automated code review. sonarsource.com/pragmatic/?utm_medium=paid&utm_source=pragma… • WorkOS – Everything you need to make your app enterprise ready. workos.com/ — *The Pragmatic Engineer deepdives relevant for this episode:* • AI Engineering in the real world newsletter.pragmaticengineer.com/p/ai-engineering-in-the-rea… • The AI Engineering stack newsletter.pragmaticengineer.com/p/the-ai-engineering-stack • Pressure on commercial open source to make more money – and HashiCorp changing its license newsletter.pragmaticengineer.com/p/the-pulse-64 • How Linux is built with Greg Kroah-Hartman newsletter.pragmaticengineer.com/p/how-linux-is-built-with-g… — *Where to find Mitchell Hashimoto:* • X: x.com/mitchellh • LinkedIn: linkedin.com/in/mitchellh • Website: mitchellh.com • Ghostty: ghostty.org • How Mitchell adopted AI: mitchellh.com/writing/my-ai-adoption-journey — *In this episode, we cover:* () Intro () HashiCorp origins () Early cloud computing () The 2010s startup scene in SF () Funding HashiCorp () The "Hashi stack" () An early failure in commercialization () The open-core pivot () Taking HashiCorp public () The almost-VMware acquisition () Mitchell’s take on AWS, GCP and Azure () AI’s impact on open source () Ghostty () How Mitchell uses AI () Open source + AI () The problem of Git and monorepos () Mitchell’s hiring practices () Mitchell’s AI adoption journey () Advice to future founders () What’s changing for software engineers () Closing — See the transcript and other references from the episode at newsletter.pragmaticengineer.com/podcast — Production a

Why it's here

1 person recommends this

What people say. Recommended for its reasoned stance on LLMs and strategies for dealing with AI-generated open-source contributions.

Moments people linked to

u/AnUnshavedYakin r/rust • Recommends

On “Redox OS has adopted a Certificate of Origin policy and a strict no-LLM policy”

For a real world example, Mitchell Hashimoto goes over how AI is affecting OSS in Ghostty. He has quite a reasoned stance on LLMs, he's definitely not anti-LLM, and still he suffers from this flood. He talks about several strategies for dealing with OSS LLM contributions in that whole talk iirc, but i highlighted a relevant part if my memory serves me.
56View on Reddit

u/kwertieein r/rust • Mentions

On “AI slop PRs are becoming a real pain to deal with”

Well yeah Mitchell is not strictly anti-AI, he just doesn't like the 100% AI contributions. And I thought he said in an interview that he did track who vouched who, but I can't find it in the repo as well. I assume he just keeps it as simple as possible while still practical
1View on Reddit