My AI habits were built around "is this worth the money?" My new job runs on "make this work." Turns out the scarcity I designed around was never a property of the technology. The ceiling is higher than I thought. Here we go.

Chrome is fast, secure and compatible. It’s also built by an advertising company. I tried the alternatives and ended up with Zen and Brave. Rooting for Ladybird!

AI agents scrape valuable work for free. Paywalls punish one-time readers. There’s a better option: give the agent a wallet.

314 MEPs voted to kill Chat Control. 276 backed it. It survives until 2028 anyway, because in EU procedure, absence can outweigh votes cast.

AI agents forget the plot between sessions. AI Task Manager gives them a local workflow built from markdown tickets, folders, and a lightweight kanban board, so project context survives different agents and sessions.

The industry decided that simple infrastructure is for beginners and distributed complexity is for serious engineers. I disagree.

Call this "part 2" or just the “I-send-this-when-someone-says-Windows-is-fine-for-devs” edition. Old long post is here. Easy shots * Corpo bloat: macOS & Linux handle corporate bloat gracefully. Windows somehow manages to fight itself into lags * Builds: Same hardware. Same IDE.

A supposedly “Pro” Samsung 990 NVMe turned my home server into a biweekly reboot ritual. Meanwhile, a forgotten SK Hynix laptop SSD ran flawlessly for five years. Here’s how a boring Goodram and a FireCuda 530R restored my faith in hardware.

You know what? I miss when tech was quiet. Not "boring". Just quiet. You’d sit down, open your IDE, maybe browse a few blogs or forums, tinker with some open-source repo. It felt like a craft: like carving wood, or doing art, in a way. Now?