News for hackers. Stuff that matters.

A comment on DuckDB Internals: Why Is DuckDB Fast? (Part 1). Parent comment

Re:DuckDB Internals: Why Is DuckDB Fast? (Part 1) by cyanide911 on Friday June 19, 2026 @03:36AM (#48595874)
>Recently at work I've been using it to analyse the Claude code sessions of every engineer at our company (that we upload to S3) and it's been extremely helpful to help us find gaps in devex and have clear metrics to back up the impact of fixing them

Nice! How do you set things up so that your engineers's claude code sessions upload to S3? Thanks for the help in advance

[ Parent | on HN ]
Re:DuckDB Internals: Why Is DuckDB Fast? (Part 1) by pimeys on Friday June 19, 2026 @07:07AM (#48597239)
If you use OpenCode, the sessions are all in a local sqlite database. After lunch I'm pushing one of my agents to crunch some data from that using duckdb...
[ Parent | on HN ]
Re:DuckDB Internals: Why Is DuckDB Fast? (Part 1) by _boffin_ on Friday June 19, 2026 @09:37AM (#48598428)
Probably on a business / Enterprise plan, which has managed settings and also telemetry export. Give it a collector endpoint to export to and then have collector send to s3.
[ Parent | on HN ]
Re:DuckDB Internals: Why Is DuckDB Fast? (Part 1) by 0xferruccio on Friday June 19, 2026 @04:25PM (#48602864)
We have a hook that runs on session start and session end that sends data to a lambda with a hard coded JWT token that we ship in the code

We added that to the managed settings for our Claude instance as a “base” plugin and provision it to all machines using JAMF

A non-enterprises version of that would be to add this hook in your main repository’s .claude folder

[ Parent | on HN ]