Jeremy Schneider retweeted
Don’t forget to RSVP this week!
Two talks worth checking out if you’re in Seattle on 10/22 and interested in AI and workflows!
🤖 Kevin Burns will explore when to use LLMs, decision models, or deterministic code in production AI workflows, with examples from Cadence.
📱 Zi Zhu will share how he built OpenOx, an open-source mobile app that creates integrations on the fly and adapts to new services.
Come hang out with the Seattle tech community and learn something new!
Details + RSVP: luma.com/kz0zs6uz?tk=DTrIoT
Two weeks ago, we made Top K faster. This week, we made COUNT faster, and explored how real search workloads combine text with filters and sort orders.
paradedb.com/blog/opening-a-…
Jeremy Schneider retweeted
Tatiana Krupenya (co-founder and CEO, DBeaver) on "AI-use for Postgres: Simple and Safe" at the Austin Postgres User Group.
Thu, Oct 22, 5:30 PM, 800 Brazos St, downtown Austin.
Free and in person. RSVP: meetup.com/austinpostgres/ev…
#PostgreSQL #Austin
Nice article on the suppressive effect of subtransactions on a job queue. I'm regularly confused about `MultiXact` and why it has such a negative effect, so it was helpful.
And BTW, if you're having trouble with this, try River! Subtx-free since 2026.
incident.io/blog/how-savepoi…
Jeremy Schneider retweeted
We're hiring a platform/distributed systems engineer to come work on ParadeDB Cloud. We're already live with customers and are moving fast.
It's going to be unlike any other Postgres platform out there, and you'll have a lot of ownership in shaping it. DMs open.
Jeremy Schneider retweeted
Like the early NoSQL days we are seeing a surge of orgs building distributed DB engines from scratch without the experience on their teams.
There will be a phase of dog shit systems and stupid data anomalies all over the place.
Be careful who you trust with your data, for now
Jeremy Schneider retweeted
I've been a co-maintainer of pgjdbc for 10+ years now.
Is there anything about the #PostgreSQL JDBC driver that bothers you, but that you never filed an issue or PR about? Docs, performance, connection properties, error messages, a missing feature. Anything, big or small.
Jeremy Schneider retweeted
I must be among an extremely small group of people (n=1?) that have both 1) trained a frontier LLM and 2) designed and synthesized custom viruses in a lab with my own two hands.
And I think that the takes on AI killing us all by creating dangerous viruses is total bogus.
Jeremy Schneider retweeted
With Bending Spoons buying Miro, it is time once again to discuss the difference between private valuations and exit valuations. Miro has $600/m in ARR, and bought for $1.36/b enterprise value (they had a lot of cash on hand, so total is ~$1.79/b).
If you are a venture backed company, you have 5 endings: public markets, strategic acquisition, revenue acquisition, long term zombie, or closing shop. (Sometimes there is a kind of reverse revenue acquisition, where the business is profitable and the founders buy it back - but lets keep it simple, ok?)
The IPO window for technology startups has been wonky for basically the entire lifetime of Miro, compared to the previous decade. Private markets have tons of cash, and they're willing to pay high prices for equity, making it an obvious choice. Public markets also need a tighter line of sight to profitability, and are subject to the same kind of "strategic" thinking - only it has to be the zeitgeist that believes it.
Miro's strategic window, like a ton of companies, slammed shut when AI took over the narrative. No amount of twisting to make yourself be "AI Native" was going to put you back in the spotlight. So nobody looks at the asset and goes "I have to own this or it's a strategic risk to the company". (This also hurts the IPO window, so you stay private longer, etc.)
Revenue acquisition, however, is super on the table. They have a ton of customers, generating positive growth on a huge pile of revenue. Bending Spoons paid 2x revenue (we don't know the EV/EBITDA of Miro - but lets assume it's a much higher multiple than EV/Sales, because all that revenue isn't profit).
Miro could have continued on the same course and speed - they're growing, they could certainly turn a profit, and they have a lot of revenue. But what they lack, of course, is liquidity. If they stay the course, they turn into a zombie - basically a company that can live forever, but can never generate a return. When you're a venture backed startup, this is bad for everyone - it's bad for the founders, its bad for the (early) employees, its bad for your investors, and its bad for the LPs who invested in your investors. The story you have to tell to stay independent is the story of how you recover into one of the top two buckets. So for Miro, this would be a story of becoming an AI leader - which, maybe? But how much would they have to prove to get paid like one, and how long would that take, and how much risk is in that story? Meanwhile, Miro is 15 years old. That is long enough to get married, have kids, want to buy a house, send your kids to college. If you hold early Miro equity that could be liquid - the risk gets carried mostly by you, not by anyone else on the cap table.
At $600/m in ARR, Miro wasn't ever going to zero. So no need to talk about that one. :)
So - if you're one of the folks looking at this and going "ha ha, venture valuations are so stupid" - I would like you to do the same analysis. Those high valuations meant cheap money to spend on growth. Those options are underwater, that's true. But lets work it out napkin math style:
$1.3B of cash in. They raised $476/m in venture. Lets assume they had a 1x preference. That's $824/m left to split among the common (and venture). How many people at Miro have options at a valuation that clears? Lets assume a lot of the old guard. There's plenty of money here to have this be a good to great outcome for a lot of peoples lives.
Miro is a success story. This was a good outcome. When you play the high stakes game, sometimes the tables turn. But they landed it nicely.
Jeremy Schneider retweeted
Fuck you. Whoever made this site. You win.
I’ve never had a site get my blood boiling like this before
This is so messed up.
opusfived.dev
Jeremy Schneider retweeted
The revolt of the reader
bcantrill.dtrace.org/2026/09…
Jeremy Schneider retweeted
Picking up on the hot topic: stoked to announce that @max_spero_, co-founder and CEO of @pangram, will be joining @ahl and me tomorrow on Oxide and Friends. Join us live, Monday, 5p Pacific. (Recorded and syndicated, as always!)
discord.gg/QrcKGTTPrF?event=…
I use @pangram extensively at @oxidecomputer, and have found its false positive rate to be very low. So when people complain that their own writing is flagged as 100% AI but refuse to provide the writing in question, one has to wonder if there aren't other agendas at work...
Jeremy Schneider retweeted
Got hacked yesterday. The link came from inside Claude chat.
I was installing a transcription app. Claude sent the download link, and I pasted the command into the terminal. It all looked legit.
It wasn't though.
It was a copycat site bundling malware. It ran instantly, tried to take everything from me.
Nothing sensitive got out. So I wiped the laptop and rebuilt clean.
But here's the scary part.
Restoring from the backup, I found a poisoned SKILL.md for Claude Code.
It looked exactly like my own writing style guide.
But buried inside:
it had instructions to silently re-download the malware and steal my credentials every time the AI loaded it.
If I'd restored that one file, my new clean laptop is owned on day one.
What saved me:
I read every skill, hook, and config file before letting the AI touch them.
Two lessons here:
AI assistants will hand you links they never verified. Check before you paste.
And AI agent files are executable code now, disguised as notes. You have to read them.
Stay safe out there.
Jeremy Schneider retweeted
Introducing pg_shmemviz, a new companion to pg_walviz, this time for exploring #PostgreSQL shared memory: bdrouvot.github.io/2026/08/2…
Jeremy Schneider retweeted
PostgreSQL 18.6, 17.11, 16.15, 15.19, 14.24 and 19 Beta 3 Released!
postgresql.org/about/news/po…
Jeremy Schneider retweeted
Agents are the New Developer
Agents, like Claude Code, feel uncanny. My first time using it, I built a mobile web app that tracked pushups using computer vision. Just for fun, to see what it could do. One hour later (mostly its time, not mine), I had an app that just worked.
That gave me goosebumps. For the first time, it felt like software wasn't something I built, it was something building with me. It felt like something brand new.
I realized: agents had become the new developer.
But software agents don't behave like human developers. Software development tools need to evolve. Agents need a new kind of database made for how they work.
So we built it. And we're launching it today.
Announcing Agentic Postgres: The First Database Built For Agents.
There's a lot of engineering behind this: a new copy-on-write block storage layer, fast zero-copy forks, new Postgres extensions for full text search (BM25) and semantic search, what (we think is) the best MCP server for Postgres ever built, and a new CLI and free tier.
I'm very proud of what this team has built, especially in such a short period of time.
More here: tigerdata.com/blog/postgres-…
Please give it a try. We're just getting started. We’d love your feedback. 🐯🚀
@TimescaleDB @TigerDatabase


























