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
The Pragmatic Engineer published an episode featuring Peter Mattis, Cockroach Labs co-founder and CTO, on distributed databases, storage engineering and AI-assisted coding. The discussion draws on his work at Google and Cockroach Labs, but the source does not provide a publication date or new product announcement.
The Pragmatic Engineer has published an episode featuring Peter Mattis, the co-founder and CTO of Cockroach Labs, on how engineers build fast, reliable distributed databases and storage systems. Mattis discusses lessons from Google’s storage infrastructure, his path from open-source software to database development, and his view that AI tools have made him more productive at writing code.
In the episode, Mattis reflects on engineering work spanning GIMP, Google and Cockroach Labs. He and college roommate Spencer Kimball created GIMP, the open-source image editor. The report says the first version of the Google logo was made using GIMP. Mattis later worked on Gmail and distributed storage at Google before co-founding Cockroach Labs.
The conversation connects database design to examples from that work. Gmail’s early storage layer used B-trees to track email threads and unread counts, with messages matched to threads through a search index. At Google, Mattis also built a B-tree with semantics similar to C++’s std::map after noticing the standard structure in memory profiles. The report says it was faster and smaller in that use, and that Google used it internally.
Mattis describes Colossus, Google’s successor to the Google File System, as a storage system that used Reed–Solomon erasure coding. The source says it reduced storage overhead by 33% while increasing redundancy: instead of keeping three full copies, the system stored data twice using erasure coding. The episode also covers Mattis’s work on a Swiss Table implementation for Go; according to the report, the implementation later entered Go’s standard library with help from the Go team.
Alongside the systems discussion, Mattis talks about returning to hands-on coding with AI tools after his work had shifted toward management. The report says he believes AI can improve code quality and increase the impact of domain experts. It also previews discussion of code review and engineering skills. These are his views as presented in the episode, not results from a controlled study.
Lessons from Google’s Storage Systems
The episode gives readers an account of how concrete engineering choices can affect storage cost, speed and reliability. The Colossus example illustrates the tradeoff: erasure coding can reduce the amount of stored data while maintaining redundancy, compared with storing multiple complete copies. The report’s 33% figure describes Google’s file storage overhead reduction; it does not give a measurement period or further detail on how the figure was calculated.
Mattis’s examples also show why data structures matter in systems work. B-trees appear in the report’s account of Gmail, an internal Google replacement for std::map, and CockroachDB’s range index. His AI comments add a current engineering perspective: an experienced developer’s assessment may interest teams adopting coding assistants, though the episode summary does not quantify productivity or quality changes.
Top picks for "distribut databas peter"
As an affiliate, we earn on qualifying purchases.
From GIMP to Distributed Storage
Mattis’s career, as outlined in the report, spans open-source software and large-scale infrastructure. He created GIMP with Spencer Kimball before joining Google, where he worked on Gmail and distributed storage. He later co-founded Cockroach Labs, whose database work is part of the episode’s discussion of distributed systems.
The source recounts that Mattis initially declined an offer from Sergey Brin because he did not want to commute from San Francisco to Mountain View. He joined another startup, then accepted a later opportunity at Google. The report also says Mattis and Kimball nearly delayed GIMP after hearing about a competing photo editor, but chose to ship their project. Mattis’s advice to founders was: “There’s always going to be someone else working on your idea.”
““There’s always going to be someone else working on your idea.””
— Peter Mattis, as quoted in The Pragmatic Engineer report
What the Episode Does Not Establish
The supplied report does not state when the episode was published, provide a full transcript, or give measurements for Mattis’s personal coding output or the effect of AI on code quality. It says he previously shipped about 100,000 lines of database-grade code per year before AI and now feels more productive, but gives no measurement method or comparison period for that assessment.
The Colossus account includes a 33% reduction in storage overhead, but the source summary does not identify the underlying study or explain the calculation. The discussion of network latency—from milliseconds for within-zone round trips when Colossus was built to about 100 microseconds today—is also presented without a date range or technical measurement details. These figures should be read within the source’s stated context.
Where Readers Can Hear More
The episode is available through YouTube, Apple and Spotify, according to The Pragmatic Engineer. The report directs readers to the episode transcript near the top of its page and timestamps at the bottom. It does not announce a follow-up episode, a Cockroach Labs product release or a scheduled next milestone.
Readers seeking more detail on the claims can consult the linked episode and transcript. Further information about the storage figures, the precise AI coding comparison and the timing of the episode is not included in the supplied source material.
Key Questions
Who is Peter Mattis?
Peter Mattis is the co-founder and CTO of Cockroach Labs and an original creator of GIMP. The report also describes his work on Gmail and distributed storage at Google.
What does the episode cover?
The episode discusses distributed databases, storage reliability, data structures and AI-assisted coding, drawing on Mattis’s experience at Google and Cockroach Labs.
What did Colossus change?
According to the report, Colossus used Reed–Solomon erasure coding and reduced Google’s file storage overhead by 33% while increasing redundancy, compared with the earlier approach of storing three full copies.
Did the source measure AI’s effect on Mattis’s coding?
No quantitative study is described. The report says Mattis feels more productive with AI and believes it can improve quality, but it gives no measured comparison of productivity or code quality.
Source: rss
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
