Jeremy Taylor

Working on @xtdb_com

#ToolsForThought obsessive, 4GL maximalist (SQL is alright), always happy to chat :)

[Jeremy Taylor @refset]

@juxtpro @xtdb_com @lukaseder This one was a really enjoyable chat - jOOQ is an impressive project that has been delivering typesafe & SQL-centric database goodness for far longer than most developers have cared about such things.

Good ideas stand the tests of time 🏆

[Strace @straceX]

Somehow a 100-line SQL query is considered unmaintainable, but splitting the same logic across five services and a message queue is considered architecture.

[Gary Bernhardt @garybernhardt]

It's amazing that just a few years ago, AI fears would get responses like "we wouldn't just give them uncontrolled access to our computers." How many computers run a coding agent in YOLO mode per day? Arbitrary code execution, usually on admin accounts, with full internet access.

[Andy Matuschak @andy_matuschak]

⭐ New talk! https://t.co/dhDLxakvrC

Coding agents might help us finally break out of two cages: the app model, which traps computing in one-size-fits-all silos; and programming as a specialization, which has crowded out cultures of imagination and domain insight.

[Jeremy Taylor @refset]

@truskovskiy We use Claude a lot for working on @xtdb_com, but mostly as a debugging tool and research/experimentation assistant. The hard code still requires lots of human brain power, for now. I expect the landscape will shift more quickly on the pure OLAP side, e.g. https://t.co/w3ES2RjkzE

[Orion Reed @OrionReedOne]

Software is not soft. It arrives rigid, opaque, and brittle. The most malleable medium we have produced is, in practice, among the least malleable materials we encounter in daily life.

[Jeremy Taylor @refset]

The theme of @CMUDB's ongoing Future Data Systems seminar series is "what should a database system look like in the future to handle more of our past so we never forget" - clearly I'm biased, but the answer has to be @xtdb_com ! Join us live on 24th November to learn more...

[Jeremy Taylor @refset]

@xtdb_com @narayanarjun If anyone else fancies booking a slot to meet and chat similarly, DMs are open :)

[XTDB @xtdb_com]

In the build up to an official XTDB v2 release we are running a series of informal chats on our Discord server - come join!

This Friday we're speaking with @narayanarjun who has battled many times with as-of chaos during his time at Materialize - see https://t.co/qhgf3w1tHX

[XTDB @xtdb_com]

🕰️ Ever needed to track exactly when data was valid, or how it changed over time?
🔎 XTDB makes historical data management seamless with #bitemporality, letting you query past states, track expiring records, and analyse changes—all with precision and control. (1/3)

[XTDB @xtdb_com]

"Handling the element of time in SQL has been a challenge since it was created"

"current databases require you to manually insert time values that track when a data item was added, when it became valid, and when it became invalid"

Reflections by @Intellyx's Eric Newcomer [1/2]

[XTDB @xtdb_com]

💡Struggling with tracking data changes/mistakes in SQL #databases?
🌟XTDB introduces powerful tools to handle historical data, from managing corrections with soft deletes to permanently erasing records, XTDB offers bitemporal capabilities that SQL alone can’t provide!
(1/3)

[Heart of Clojure @heartofclojure]

@refset shares his vision for how to make SQL better and more fit for the future by making it more compatible with #Clojure’s philosophy: https://t.co/7R3hFQjQJq

[XTDB @xtdb_com]

"SQL queries start with SELECT" has been true for 50 years, but what could we unlock by allowing you to start a query with FROM instead...?

Check out our latest beta5 release to learn more - featuring some rather exciting SQL pipelining and templating capabilities [1/2]

[XTDB @xtdb_com]

🚀 Need accurate reporting and seamless data corrections in your #Database?
📹 See how XTDB's bitemporality makes auditing and historical queries effortless. Correct mistakes, track changes, and retrieve past states—all with simple SQL queries.

(1/2)

[Dustin Getz @dustingetz]

I am just having the time of my life building lightning fast complex virtual scrolled tables with server-streamed differential record spooling over 10k records ... in 12 lines of simple, straightforward code. #ElectricClojure

[Jeremy Taylor @refset]

@eirikbakke Sounds quite a lot like "streamed differential record spooling" https://t.co/mJLJPnyKmL

[Dustin Getz @dustingetz]

I am just having the time of my life building lightning fast complex virtual scrolled tables with server-streamed differential record spooling over 10k records ... in 12 lines of simple, straightforward code. #ElectricClojure

[Jeremy Taylor @refset]

@RealGeneKim @eirikbakke @ultorg 💯 Incidentally, I would love to get you and @ryrobes in the same room :) https://t.co/50SHDl15ZH

[Ryan Robitaille @ryrobes]

XTDB Bi-Temporal SQL. Time-travel scrubbing.
IYKYK.

The "as-is vs as-was" convo is dead.

[Nathan Marz @nathanmarz]

The older I get, the more amazed I am that John McCarthy invented Lisp in 1958 when the popular programming languages were Algol, Fortran, and Cobol. 66 years later and it's still mind-blowing to the vast majority of the industry.

[JUXT @juxtpro]

🎁 Day 1⃣🎱– JUXT Content Advent Calendar 🎄🗓️

@RealGeneKim – bestselling author of The Phoenix Project The DevOps Handbook – joins @malcolmsparks & @refset to discuss modularity, AI, and innovation in software development.

🎧 Full episode here ➡️ https://t.co/n6ZXLsn7mO

[XTDB @xtdb_com]

Can we do better than JSON_AGG? #SQL has had sub-queries since SQL:92 - but it's still a challenge to return properly nested data through SQL queries.

#XTDB delivers first-class support for nested values, as well as `NEST_ONE` and `NEST_MANY`, which fill this gap. 1/n