Jeremy Taylor

@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 🏆

@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. arxiv.org/abs/2603.02001

Finally finished the Future Data Systems Seminar Series - Fall 2025. All 12 talks. (I know, I'm a bit slow) Great series - deep, genuinely technical, no fluff. One question kept coming back to me with every talk: how much AI coding (Claude, Codex, Cursor) are these teams actually using? For SaaS, CRUD apps, UI work - the answer is obvious. But for low-level database internals, storage engines, query planners in C/C++/Rust - how much does AI help there? I'd genuinely love to know. @byte_array @jrdntgn @willmanning @ianmcook @refset @jarkwu

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.

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...

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

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 github.com/orgs/xtdb/disc…

🕰️ 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)

"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]

💡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)

@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: youtu.be/ot4DDcEHhLs

"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]

🚀 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)

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

@eirikbakke Sounds quite a lot like "streamed differential record spooling" x.com/dustingetz/sta…

There's a lot of housekeeping involved relating to multi-threading, query cancellation, LIMIT clauses, error-handling, and so on. And optimizations to avoid issuing new SQL when previous results would satisfy the new version of the query (e.g. after hiding a column). (3/5)

Making a fast, responsive UI for a slow external process is a bit of an art. In @Ultorg's case, the user builds database queries through a spreadsheet-like UI. The queries are compiled to SQL and executed remotely--but the UI doesn't actually wait for the results! (1/5)

@RealGeneKim @eirikbakke @ultorg 💯 Incidentally, I would love to get you and @ryrobes in the same room :) x.com/ryrobes/status…

@eirikbakke @ultorg Cc @refset One more reason to switch to xtdb v2 — leverage all the amazing SQL tooling out there. (Came up with a couple more super compelling reasons after our interview/conversation!!)

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.

🎁 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 ➡️ juxt.pro/blog/gene-kim-…

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

XTDB is built for a world with ever increasing regulation and scrutiny over decision making - making data and applications transparent to users and developers alike. Register now if you'd like to hear more zoom.us/webinar/regist… 2/2

I'm giving an online tech talk with @FINOSFoundation this Wednesday (4pm GMT) on 'as-of reporting' in financial services - but really this applies to all organisations who care about the auditability of systems. XTDB helps you to quickly figure out how data has changed and why /1

Are JSON columns and versioning painful in your existing databases? Probably! 📹 Check out this short tour through some of XTDB's novel SQL features for handling semi-structured data ('records') and as-of queries.