Johnny Graettinger

Co-Founder & CTO, Estuary · 1 appearance on the record.

computed by AI from the episodes · how this works → · full disclaimer →

founderexecutiveengineerestuary.dev ↗

Johnny Graettinger is the co-founder and CTO of Estuary, where he architected and oversees Estuary Flow, a real-time data streaming platform. Earlier in his career, he worked as a Chrome networking engineer at Google, co-founded Arbor, and created the open-source Gazette streaming infrastructure project.

6statements → 4claims → 3claims resolved → 100%fully supported → 4.5/5average certainty → 1.17/5average debate potential →

3 supported 0 partly supported 0 contradicted 1 not checkable as stated how the 4 claims stand · each chip opens the sources

4 assertions · 2 disclosures · every statement was checked. The predictions and assertions are the 4 claims: statements the public record can support or contradict. 3 are resolved, and 1 names no date, number or outcome precise enough to check. Everything else (opinions, insights, what ifs, disclosures) can never be settled by the record, so it carries no assessment.

The record, in short

What the tape says about how Johnny argues and how the claims held up. Everything they said, and everything said about them, is in the tabs below.

Their most notable supported claim

Assertion Supported
Graettinger: Estuary Flow processes data incrementally by tracking changes
“Flo's really concerned with just the movement of data through this topology through the data systems that you have, and it's doing it in a very incremental way. So it's looking just at what's changing within any given collection and propagating the effects.”
Johnny Graettinger Aug 11, 2022 ▶ 3:29 Building Real-Time Data Pipelines | Estuary's Johnny Graettinger

Expressed certainty vs assessment result

none yet certainty 1
none yet certainty 2
none yet certainty 3
100% certainty 4
100% certainty 5

weighted support: a fully supported claim counts one, a partly supported claim counts half. Each filled bar is clickable and opens exactly those claims; "none yet" means nothing said at that certainty level has resolved yet

How they sound: speaking style how? →

256 words/min while actually speaking · 46.1 um and uh per 1k words

No argument clarity score for Johnny Graettinger: only 1 usable question→answer exchange on raw tape (a fair score needs 8+). We do not score a sample that small. Roundtable and news formats yield far fewer direct exchanges than interviews.

Measured by listening to the audio itself: 3,555 words across 1 episode of raw-level tape, transcribed verbatim with every um and uh kept, each one attributed only where the alignment onto our timed stream is unambiguous. These are measurements of speaking style. We do not rank them: across this corpus, fluency and argument quality are nearly uncorrelated (ρ≈0.2), and smooth talking does not signal clear thinking. How it's measured →

Everything Johnny Graettinger said on the MAD Podcast that made the record, most notable first. Filter by type, assessment or year in the ledger →

Disclosure
Graettinger: Estuary Flow is not a database and stores no data copies
“But a key thing to understand about Flow is that it is not a database. It is not storing copies of your data. It is really concerned just with coordinating your existing data systems and how data is moving between them.”
Johnny Graettinger Aug 11, 2022 ▶ 2:22 Building Real-Time Data Pipelines | Estuary's Johnny Graettinger
Disclosure
Graettinger: Estuary charges customers based on compute resource usage
“We're charging on usage, essentially. So we're charging on the actual, like, compute resource that's required in order to get these workflows up and running.”
Johnny Graettinger Aug 11, 2022 ▶ 19:04 Building Real-Time Data Pipelines | Estuary's Johnny Graettinger
Assertion Supported
Graettinger: Estuary Flow processes data incrementally by tracking changes
“Flo's really concerned with just the movement of data through this topology through the data systems that you have, and it's doing it in a very incremental way. So it's looking just at what's changing within any given collection and propagating the effects.”
Johnny Graettinger Aug 11, 2022 ▶ 3:29 Building Real-Time Data Pipelines | Estuary's Johnny Graettinger
Assertion Supported
Estuary's materialization connectors are implemented as Docker container plugins
“Connectors for materializations are essentially Docker container plugins.”
Johnny Graettinger Aug 11, 2022 ▶ 4:24 Building Real-Time Data Pipelines | Estuary's Johnny Graettinger
Assertion Supported
Graettinger: Google Sheets rate limits updates faster than once per second
“That's actually a limitation of Google Sheets. If you try and make updates to Google Sheets any faster than that, Google starts to rate limit you.”
Johnny Graettinger Aug 11, 2022 ▶ 8:19 Building Real-Time Data Pipelines | Estuary's Johnny Graettinger
Assertion Not checkable as stated
Graettinger: Estuary Flow collections enable reuse without impacting source databases
“So these collections are, can, you know, can be repeatedly used for different downstream kind of data processing tasks without ever impacting or touching that database again.”
Johnny Graettinger Aug 11, 2022 ▶ 10:52 Building Real-Time Data Pipelines | Estuary's Johnny Graettinger

Appearances (1)

EpisodeDateSpeaking time
Building Real-Time Data Pipelines | Estuary's Johnny Graettinger Aug 11, 2022 17m
Made with StarZero

Turn any episode into a week of clips.

This entire site, over 400 conversations transcribed, diarized, checked and made playable, runs on the StarZero media pipeline. Drop in your own episode and the podcast clipper finds the moments worth sharing, cuts them, captions them, and reframes them for every feed.