TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
In an interview with The Pragmatic Engineer, Cockroach Labs co-founder Peter Mattis discussed lessons from building storage systems at Google and distributed databases at Cockroach Labs. He also described how AI tools have brought him back to writing code, though the interview does not provide measurements of productivity or code quality.
Peter Mattis, co-founder and chief technology officer of Cockroach Labs, discussed how engineers build storage and database systems that remain fast and reliable as they scale in an interview published by The Pragmatic Engineer. The conversation also covered his earlier work at Google and his view that AI coding tools have brought him back to writing code after his work shifted toward management.
Mattis described work on Gmail’s early storage layer, where B-trees tracked email threads and unread counts. The interview’s account says incoming messages were matched to threads using a search index. It also revisits Colossus, Google’s successor to the Google File System, where Mattis and colleagues used Reed–Solomon erasure coding to store data with two copies while increasing redundancy compared with the earlier system’s three full copies.
The discussion connects those experiences to distributed database design and CockroachDB. Mattis pointed to B-trees as a recurring structure in storage systems, including Gmail’s backend and CockroachDB’s range index. At Google, he also built a B-tree alternative to the red-black tree used by C++’s std::map, which the source says was faster and used less memory. Separately, he developed a Swiss Table implementation for Go that later entered the language’s standard library with help from the Go team.
On AI, Mattis said the tools have made him feel more productive and returned him to hands-on coding. The interview frames this as his personal experience and argument: AI may improve quality and increase the impact of engineers with deep domain knowledge. The source does not provide independent productivity measurements or comparative code-quality results.
Lessons From Google’s Storage Systems
The examples show how data structures and storage formats shape the performance, memory use and resilience of systems used at large scale. Colossus’s use of erasure coding illustrates one way a storage system can reduce the overhead of keeping full copies while maintaining redundancy. The interview does not give enough technical detail to assess the design independently, but it presents the change as a concrete example of engineering tradeoffs.
Mattis’s account of returning to coding with AI tools is relevant to software teams weighing how these tools affect experienced engineers. His experience suggests a possible change in how senior engineers spend their time; it does not establish that AI improves productivity or quality across teams. The interview also raises the practical question of how code review should adapt as engineers produce code with AI assistance.
Top picks for "distribut databas peter"
As an affiliate, we earn on qualifying purchases.
From GIMP to Cockroach Labs
Mattis first became known as a co-creator of GIMP, the open-source image editor he developed with college roommate Spencer Kimball. The source says the first version of the Google logo was made using GIMP. Mattis later joined Google after initially declining an offer because of the commute from San Francisco to Mountain View.
At Google, his work included Gmail and distributed storage. He later co-founded Cockroach Labs, which builds CockroachDB, a distributed SQL database. The interview uses this path—from open-source software to large-scale storage and database development—to discuss how engineering choices affect systems as they grow.
“There’s always going to be someone else working on your idea. You can’t get dissuaded if they pre-announce it.”
— Peter Mattis, as quoted in The Pragmatic Engineer
AI Gains Remain Unmeasured
The source does not state the interview’s publication date or provide benchmarks for Mattis’s reported productivity, code quality or AI use. It also does not specify how widely his experience applies to other engineers, or how code review practices should change. Those points remain open questions rather than established outcomes.
Further Discussion of Engineering Work
The source directs readers to the full interview, its transcript and episode timestamps, and says the episode is available on YouTube, Apple and Spotify. It does not announce a specific follow-up study, product release or policy change. Further evidence about AI’s effects would require published measurements across defined tasks, teams and time periods.
Key Questions
What is the interview about?
The Pragmatic Engineer interview covers Peter Mattis’s work on GIMP, Google storage systems and Cockroach Labs, along with his views on distributed databases and AI-assisted coding.
What role did B-trees play in the examples discussed?
The source says B-trees were used to track Gmail threads and unread counts. It also describes a B-tree alternative to C++’s std::map implementation and CockroachDB’s range index.
What did Colossus change about Google’s storage?
According to the source, Colossus used Reed–Solomon erasure coding to store data twice while increasing redundancy compared with the three full copies used by the earlier Google File System. The interview summary does not give further technical details.
Did the interview prove that AI makes engineers more productive?
No. Mattis described his own experience of feeling more productive and returning to coding, but the source provides no independent measurements showing how AI affects productivity or code quality across engineers.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
