Every Mac comes with a firewall, and it is switched off. This post explains what that firewall does, why turning it on is a small but free win, when a second firewall for outgoing traffic is worth installing, and why on a work Mac the decision is not yours.
A laptop with 16–32 GB of memory can answer questions about your own notes, code and unfinished ideas, and none of your data leaves the computer. Choosing the model is the easy part. Two other things decide whether the answers are useful: how much memory the model has, and how well it finds the right pages of your files. Without them, it just guesses, and it sounds sure even when it is wrong.
Nearly every software company keeps its most valuable asset on a platform somebody else owns: GitHub, GitLab, Bitbucket, or one of a handful of smaller hosts. Your git history can leave any of them in an afternoon — almost nothing else you built there can, so who owns the platform matters more than its feature list.
An artificial intelligence (AI) router sits between your app and the model providers and decides, per request, which model answers. "Router" names three different jobs — a gateway, a fallback chain and a smart router — and each hands over more of a decision that used to be yours.
For fifteen years the .env file has been the most convenient lie in web development: a plaintext file full of production-grade credentials, kept safe by the single assumption that only you would ever read your own disk. That assumption is now false, and the fix is less dramatic than it sounds.
TypeSafe AI launched Jev on 15 September 2026 with a headline of "193.6x faster, 444.6x cheaper" and a promise that it "can't hallucinate". Read the primary sources rather than the reposts and a narrower, more interesting product appears: a frontier-trained classifier for software, not a better large language model, with every number so far reported by the vendor.
I opened Claude Code on a side project after a day away, and it greeted me with a careful reconstruction of what we had been doing, pieced together from the notes file and the working tree. It was right, but it was a guess. The whole conversation that produced that work was sitting on disk, one command away. Here is how sessions actually persist, what a resumed one gives you back, and what it never will.
Umami is a small, open-source tool that counts the visits to your website without cookies and without storing who the visitors are. This post explains how it works, what it measures, how to run it, and where its limits are.
I had seventeen live websites on seven domains, most of them on GitHub Pages, and no way to know whether anyone had ever visited them. Choosing a tracker turned out to depend on consent law and ad blockers much more than on features.
Claude Code writes two records to your disk: an append-only ledger of every exchange with the model, and a small cached snapshot of how full your rate limits are. Almost every tool and blog post about local usage tracking knows about the first one and misses the second — including, until I actually looked, me.