33 Followers
40 Following
359 Posts

I’ve finally written a deep-dive into the 250-hour build process behind syntaqlite.

While AI agents were the only reason I finally overcame the 8-year inertia to start this project, using them taught me a lot about the psychological toll of AI-assisted engineering and the trap of "vibe-coding."

The full post-mortem with journal logs and commit history:
https://lalitm.com/post/building-syntaqlite-ai/

(Thread on the key takeaways follows)

Eight years of wanting, three months of building with AI

For eight years, I’ve wanted a high-quality set of devtools for working with SQLite. Given how important SQLite is to the industry1, I’ve long been puzzled that no one has invested in building a really good developer experience for it2. A couple of weeks ago, after ~250 hours of effort over three months3 on evenings, weekends, and vacation days, I finally released syntaqlite (GitHub), fulfilling this long-held wish. And I believe the main reason this happened was because of AI coding agents4. Of course, there’s no shortage of posts claiming that AI one-shot their project or pushing back and declaring that AI is all slop. I’m going to take a very different approach and, instead, systematically break down my experience building syntaqlite with AI, both where it helped and where it was detrimental. I’ll do this while contextualizing the project and my background so you can independently assess how generalizable this experience was. And whenever I make a claim, I’ll try to back it up with evidence from my project journal, coding transcripts, or commit history5.

Lalit Maganti

There is virtually **no** AI slop security reports anymore submitted about #curl. They don't seem to happen any longer.

Almost everyone still uses AI though.

A few years ago I designed a way to detect bit-flips in Firefox crash reports and last year we deployed an actual memory tester that runs on user machines after the browser crashes. Today I was looking at the data that comes out of these tests and now I'm 100% positive that the heuristic is sound and a lot of the crashes we see are from users with bad memory or similarly flaky hardware. Here's a few numbers to give you an idea of how large the problem is. 🧵 1/5
Math trivia: the "B." in Benoit B. Mandelbrot stands for Benoit B. Mandelbrot

PSA: Did you know that it’s **unsafe** to put code diffs into your commit messages?

Like https://github.com/i3/i3/pull/6564 for example

Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!

This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.

Indeco IFP28X pulverizer with googly eyes...

Some are suggesting you deliberately write inaccurate or confusing alt text, because they say this confuses AI scrapers that are analyzing images.

The purpose of alt text is to help people who cannot see the image. Deliberately misrepresenting the image is a gross misuse of alt text. Don't do it.

If you like Rust and GDAL, you'll be happy to hear about the latest release of the Rust bindings crate, with built-in support for GDAL 3.11 and 3.12, including the new thread-safe datasets.

https://crates.io/crates/gdal

Docs coming in a point release, maybe.

crates.io: Rust Package Registry

@Fritange France is taking state actions against GrapheneOS. They're conflating us with companies which they've previously gone after and taken over their servers. We aren't vulnerable to being attacked in the same way but we still don't want accesses to our website/network services being logged or our website being hijacked. France isn't a safe country for GrapheneOS to operate in anymore and we're going to be protecting the project and our users by avoiding the country completely now.
FYI for people who have been sharing that Malwarebytes blog post about Gmail training on your email - they misunderstood and have updated their post with a correction at the top. https://www.malwarebytes.com/blog/news/2025/11/gmail-is-reading-your-emails-and-attachments-to-train-its-ai-unless-you-turn-it-off