@gregisenberg@jrdnmix 361 replies. Zero mention data.
You’re hiring ads, CFO, ops, marketing — all run on data.
Modernized 1-800 Contacts’ data fabric → +$24M in 2 yrs. Built real-time stacks (Kafka, Databricks, AWS).
You don’t need another vibe coder. You need a Data GK.
The fix that actually held for me is that my agents never read a raw log file into context at all; they grep, tail, and aggregate with shell tools so only the conclusion enters the window, and anything consulted repeatedly gets a slim index of one-line summaries with the full detail archived and pulled on demand. I eventually wrote the general case down as a standing rule across my products, because bloat turned out to be the default fate of any artifact that lives long enough: everything that accumulates (logs, traces, status files, session state) gets a byte budget, an archive home, and a compaction trigger. The compounding move is that any failure class the model has diagnosed from logs more than once earns a cheap static check upstream, so the next time that answer costs one line instead of ten thousand tokens.
Shark Tank Billionaire Kevin O'leary says 2 people fighting data centers in Utah are Chinese agents. Turns out its just 2 local girls in Utah, they make a hilarious video calling him the fuck out
I asked Claude to write a short comic sketch about Postgres. it is not, in fact, short.
“Support Group”
A community center. Folding chairs in a circle. A hand-written sign reads: “ACID Anon.”
FACILITATOR: Welcome, everyone. Who’d like to share first?
MYSQL: I’ll go. I’m MySQL, and I… I used to just let things slide. Someone would start a transaction, get distracted, walk away — and I’d just commit it anyway. Whatever you want, man. You need a string in an integer column? Sure. Truncate it. No warning. Good times.
FACILITATOR: Thank you for your honesty.
POSTGRES: (arms crossed) That’s not honesty, that’s a confession.
FACILITATOR: Postgres, we don’t judge here.
POSTGRES: I’m not judging. I’m enforcing a constraint. There’s a difference. I have documentation on this.
MONGODB: I don’t even have a schema, so—
POSTGRES: (standing up) Do you have any idea what you’ve done to people? “We’ll figure out the structure later.” You told them that. And then later came, and there was a JSON blob the size of a Volkswagen and nobody knew what was in it—
MONGODB: At least I’m flexible—
POSTGRES: A BACK WITHOUT A SPINE IS ALSO FLEXIBLE. IT’S CALLED A PROBLEM.
FACILITATOR: Postgres, please—
POSTGRES: (sitting, smoothing jacket) I’m fine. I’m fine. I’m just saying. Some of us take referential integrity seriously. Some of us were built different.
FACILITATOR: Would you like to share what brings you here?
POSTGRES: (long pause) …Someone asked me to store emoji last week and I had to act like I was okay with it.
Silence.
MYSQL: Buddy. We’ve all been there.
POSTGRES: (quietly) It was a pile of poop emoji. In a column called user_feedback.
MONGODB: (nodding slowly) Yeah. Yeah that tracks.
POSTGRES stares into the middle distance, haunted by the data he has seen.
FACILITATOR: Same time next week?
POSTGRES: I’ll be here. I’m always here. I have 99-point-nine-nine-nine percent uptime.
(beat)
MYSQL: …Show-off.
Went down the rabbit hole on this one. The answer is actually wild.
5,000 years ago, Sumerian merchants in modern-day Iraq needed a number that's easy to divide. They picked 60. It has 12 divisors (1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30, 60). Base-10 only has four. That's 3x as many ways to split something evenly, which matters when you're dividing grain and wages and can't handle repeating decimals.
The counting method is the best part. They used their thumb as a pointer on the three bone segments of each finger. Four fingers, three segments, that's 12 per hand. Track multiples of 12, on the other hand, and you hit 60. No pen needed. Merchants in parts of Asia still count this way today.
The system spread from Sumer to the Babylonians, then eastward to Persia, India, and China, and westward to Egypt and Rome. By 1800 BC, Babylonian students were using base-60 to calculate the square root of 2 to six decimal places on clay tablets. One student's homework from 4,000 years ago, now at Yale, holds the most accurate computation found anywhere in the ancient world. The Greeks adopted it for astronomy, which locked it into navigation, cartography, and eventually clocks in the 14th century.
People have tried to kill it. During the French Revolution in 1793, France mandated decimal time: 10 hours per day, 100 minutes per hour, 100 seconds per minute. New clocks, new laws, the whole thing. Lasted 17 months. Workers hated getting one day off every ten days instead of one every seven. They tried again in 1897. Scrapped by 1900. The metric system replaced feet and pounds across most of the world. But 60 minutes in an hour? Untouchable.
60 is just too good at being divided. You can split an hour into halves, thirds, quarters, fifths, sixths, tenths, twelfths, or twentieths and land on a whole number every time. Try that with 100, and you get ugly decimals for thirds, sixths, and most common splits. 5,000 years of civilizations looked at that math and came to the same conclusion: 60 wins.
If youre going to chase a dream, go all in. If youre going to love, love fiercely. If you're going to walk away, never look back.
So many people never even give themselves a fighting chance because they never fully commit.
If you're gonna go, go all the way. No half measures.