lukas.fittl.com

lukas.fittl.com

@lukas.fittl.com

84 followers85 following9 posts

lukas.fittl.com reposted

lukas.fittl.com reposted

This is excellent, one of my favorite long-form pieces on agentic engineering - includes several non-obvious ways in which leaning on coding agents can catch you out

Lalit Maganti@lalitm.com

I just published a deep-dive into the 250-hour build behind syntaqlite, a SQLite formatter and LSP I built using AI agents. AI agents were the only reason built this after 8 years of wanting but there's a psychological toll to AI-assisted engineering. The post-mortem: lalitm.com/post/buildin...

lukas.fittl.com reposted

Thank you to @pganalyze for sponsoring pgconf.dev 2026! 🐘❤️ Sponsors make this conference possible. The venue, the hallway conversations, the community that gathers every year. We couldn't do it without them. See you in Vancouver! 🇨🇦

lukas.fittl.com reposted

Reminder: code review is not "to catch mistakes", it is a tool for understanding to limit bus/lottery factor first and foremost. When code is written (if you're lucky) by one human, having the second human abdicate their judgment to the machine is actively harmful to your team's code understanding.

This post is unavailable.

lukas.fittl.com reposted

New small blog post "Measuring SELECT ... FOR UPDATE Latency in #PostgreSQL" > Are queries slow because they’re waiting to acquire locks, or because they’re taking a long time to find the actual rows? :) benoittgt.github.io/blog/postgre...

benoittgt.github.ioMeasuring SELECT ... FOR UPDATE Latency in PostgreSQLAre queries slow because they’re waiting to acquire locks, or because they’re taking a long time to find the actual rows?

lukas.fittl.com reposted

lukas.fittl.com reposted

lukas.fittl.com reposted

lukas.fittl.com reposted

Voting for unconference sessions here on Day 4 of #PGConfdev had some predictable winners (e.g. scaling PG development, multithreaded #PostgreSQL) & a few surprises too. And now the collaboration begins!

lukas.fittl.com reposted

Live now at #PGConfdev in Montreal Lukas Fittl is on stage, diving into “Tracking plan shapes over time with Plan IDs & a new pg_stat_plans”—discover how core plan‑ID tracking, partition‑aware metrics, and an extensible pg_stat_plans can revolutionize your #PostgreSQL query analy

lukas.fittl.com reposted

Over the last few weeks I've been incrementally merging infrastructure for AIO into postgres. Just now I finally merged the first actual user of AIO ("streaming reads" now can use AIO). It's been a long long road. I've been, with a lot of help along the way, working on this since some time in 2019.

lukas.fittl.com reposted

🎶 "Best practices for tuning #PostgresQL queries" will be presented by Lukas Fittl @PosetteConf 2025 (Livestream 1 on Tue Jun 10th @ 11:00am PDT (UTC-7)). 🐘 Find out more: posetteconf.com/speakers/luk... #postgres #databases #OpenSource #community

posetteconf.comSpeaker: Lukas Fittl | POSETTE: An Event for Postgres 2025Lukas Fittl, pganalyze, is a speaker for POSETTE: An Event for Postgres 2024. Lukas’s talk is titled “Best Practices for Tuning Slow Postgres Queries”.

You are up to date.