On AI agents, grunt work, and the part of science that isn't replaceable.

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.

🪨 why use many token when few token do trick — Claude Code skill that cuts 75% of tokens by talking like caveman - JuliusBrussee/caveman

Download Google AI Edge Gallery van Google in de App Store. Bekijk schermafbeeldingen, beoordelingen en recensies, gebruikerstips en meer apps zoals Google AI…

A few years ago I was in a meeting with developers and someone asked a simple question: “What’s the right framework for a new Windows desktop app?” Dead silence. One person sugges…

The Free Market Lie: Why Switzerland Has 25 Gbit Internet and America Doesn

Astronauts on the Artemis II mission are on the third day of their journey around the far side of the Moon.

Create stunning demos for free. Open-source, no subscriptions, no watermarks, and free for commercial use. An alternative to Screen Studio. - siddharthvaddem/openscreen

LÖVE is an awesome 2D game framework for Lua. Contribute to love2d/love development by creating an account on GitHub.

Little language inspired by Rust that compiles to Go.

Learn how Codex credit rates work across Plus, Pro, Business, and Enterprise/Edu plans.

I'm so excited to share nanocode. This is a library showing you how to train your own Claude Code end-to-end. To a first approximation, we will follow the simplest possible approach for training us...

Exploring tail-call-style interpreter implementation with an optimized Uxn emulator, on ARM, x86, and WebAssembly

Computational Physics

Ideally, we would have preferred to avoid this post. However, the articles and comments published in response to Collabora’s and Michael Meeks’ biased posts compel us to provide this background information on the events that led to the current situation. Unfortunately, we have to start from the very beginning, but we’ll try to keep it brief. The launch of the LibreOffice project and The Document Foundation was handled with great enthusiasm by the founding group. They were driven by a noble goal, but also by a bit of healthy recklessness. After all, it was impossible to imagine what would happen after September 28, 2010, the date of the announcement. At the time, nobody could imagine that the companies that had supported OpenOffice.org until then would create a project to kill LibreOffice. Also, if the project were to be successful, it would require resources greater than those available, and above all, a deep management experience. Fortunately, the project grew quite rapidly. However, the founders’ different backgrounds and opinions were at the same time the reason for some bold decisions – many of which right – as well as a few mistakes, which are the root cause of some of the current

Criticism can prevent mistakes. It can never create value. Only ideas can do that. The two are not equal contributions, and most meetings get this backwards.

Real-time MIDI harmony generator and guitar-to-MIDI converter. Built in Rust.