@refset

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

 UK
jdt.me
Joined April 2012
  • Tweets739
  • Following4.8K
  • Followers1.3K
53Media
Include

Only show posts containing:

Exclude

Hide posts containing:

Time range
-
Minimum likes
Jeremy Taylor retweeted
Strace
@straceXSep 11
Somehow a 100-line SQL query is considered unmaintainable, but splitting the same logic across five services and a message queue is considered architecture.
120
267
49
5,724
314,256
Jeremy Taylor retweeted
Gary Bernhardt@garybernhardtSep 12
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.
13
10
6
192
9,911
Jeremy Taylor retweeted
Andy Matuschak
@andy_matuschakApr 12
⭐ New talk! andymatuschak.org/tat 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.

Apps and programming: two accidental tyrannies

On coding agents, malleable software, and the future of interface invention

andymatuschak.org
14
73
18
663
128,138
Replying to @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

Bespoke OLAP: Synthesizing Workload-Specific One-size-fits-one...

Modern OLAP engines are designed to support arbitrary analytical workloads, but this generality incurs structural overhead, including runtime schema interpretation, indirection layers, and...

arxiv.org
1
133
Jeremy Taylor retweeted
Orion Reed@OrionReedOneFeb 26
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.
2
6
1
28
1,553
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...
1
1
4
353
Replying to @xtdb_com @narayanarjun
If anyone else fancies booking a slot to meet and chat similarly, DMs are open :)
48
Jeremy Taylor retweeted
XTDB@xtdb_com7 May 2025
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/discuss…

[ANN] Countdown to XTDB v2 - Pre-Launch Events · xtdb · Discussion #4419

We're fast approaching the moment where we flip the switch to making v2 "Generally Available" (GA) software - this means a stable API and storage format that we're prepared to sup...

github.com
1
1
5
327
Jeremy Taylor retweeted
XTDB@xtdb_com30 Jan 2025
🕰️ 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)
1
3
8
642
Jeremy Taylor retweeted
XTDB@xtdb_com20 Jan 2025
"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]
1
1
8
758
Jeremy Taylor retweeted
XTDB@xtdb_com16 Jan 2025
💡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)
1
2
1
7
995
Replying to @refset
@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

"Richer SQL — Steering SQL's Future Towards Clojure's Philosophy" by...

SELECT NAME FROM EMP WHERE DEPT = ‘TOY’…SQL has been celebrating ...

youtube.com
1
2
182
Jeremy Taylor retweeted
XTDB@xtdb_com13 Jan 2025
"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]
Standard SELECT-first SQL vs. XTDB pipeline friendly SQL

ALT Standard SELECT-first SQL vs. XTDB pipeline friendly SQL

1
1
14
334
Jeremy Taylor retweeted
XTDB@xtdb_com10 Jan 2025
🚀 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)
1
1
9
287
Jeremy Taylor retweeted
Dustin Getz
@dustingetz15 Dec 2024
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
3
10
1
86
3,097
Replying to @eirikbakke
Sounds quite a lot like "streamed differential record spooling" xitter.cf/dustingetz/status/1868…
Dustin Getz
@dustingetz15 Dec 2024
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
1
6
Replying to @RealGeneKim @eirikbakke @ultorg
💯 Incidentally, I would love to get you and @ryrobes in the same room :) xitter.cf/ryrobes/status/1845135…
Ryan Robitaille
@ryrobes12 Oct 2024
XTDB Bi-Temporal SQL. Time-travel scrubbing. IYKYK. The "as-is vs as-was" convo is dead.
1
1
3
249
Jeremy Taylor retweeted
Nathan Marz@nathanmarz16 Dec 2024
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.
2
5
1
78
4,482
Jeremy Taylor retweeted
JUXT@juxtpro18 Dec 2024
🎁 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-podca…

JUXT Blog: Gene Kim on JUXTCast: Insights into DevOps, AI, and High-Performance Technology Organi...

In this episode, Jeremy Taylor and Malcolm Sparks are joined by Gene Kim to explore the evolution of technology through modularity, AI-driven programming, and the future of innovation.

juxt.pro
3
6
971
Jeremy Taylor retweeted
XTDB@xtdb_com12 Dec 2024
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
The missing SQL sub-queries

ALT The missing SQL sub-queries

1
1
5
203
Load more