Productivity

You can revive a 2012-2015 MacBook Pro by swapping the HDD for an SSD and installing a light Linux distro. A machine that felt slow and unsupported under macOS turns into a snappy computer for web, writing, and dev work. The swap keeps working hardware out of landfill and gives you a secure, up-to-date machine for years.

Which MacBook Models Are Worth Restoring in 2026?

Not all old MacBooks make good Linux candidates. The key factor is hardware upgradability. Apple’s shift from user-serviceable to sealed hardware draws a hard line.

Software teams keep adding AI coding agents to their workflow. One popular trend: drop a repo-level context file, often named AGENTS.md or CLAUDE.md, to guide the agent. The idea sounds clean. Give the AI a map of the codebase and a few rules, and it should solve tasks faster.

But does it work? A new paper, “Evaluating AGENTS.md: Are Repository-Level Context Files Helpful for Coding Agents?” , says no. The results push back hard on the default advice.

If you reinstall Linux more than once a year, your setup is probably still too manual. Most people keep a checklist in their head: install packages, copy shell config, fix fonts, set up Git and SSH, restore editor plugins. Then they spend a week finding what they forgot. That works until it doesn’t. A failed SSD, a new laptop, or a distro hop shows how fragile the workflow is.

A better model is to treat your desktop like infrastructure: declarative, version-controlled, and repeatable. Ansible handles package and system state. GNU Stow links your dotfiles cleanly. The result is a setup you can rebuild in 20 to 40 minutes with few hand edits. It also keeps improving over time instead of drifting.

If you host your own code on a Gitea instance, you’ve likely felt the friction of cloning new projects. Opening the web UI, searching for a repo, clicking the “SSH/HTTP” button, and then jumping back to your terminal is a workflow that belongs in 2010.

If you want to “walk through” your repositories and pick what to clone directly from your terminal, here are the best tools for the job.

If your Linux dev workflow still leans on one or more VirtualBox VMs, you’re not doing anything wrong. VirtualBox has been the default pick for isolated dev setups for years: clean snapshots, clear network modes, and a full guest OS that acts just like a separate machine.

But in 2026, most app work doesn’t need full hardware emulation. It needs fast startup, easy sharing, the same deps each time, and low cost. That’s where Docker Desktop and docker compose shine.

An E-Ink monitor as a second display cuts eye strain by removing the backlight and blue light that hurt your eyes. Modern E-Ink refresh modes in 2026 make these screens usable for text work. You still need to tune your Linux theme and turn off animation. This is a niche product for a niche problem. Know what it fixes, and what it can’t, before you spend over $1,000.

Why E-Ink for Coding? The Science of Eye Strain

Screen eye strain (the clinical name is “computer vision syndrome”) has three distinct causes. E-Ink handles all three better than any LCD or OLED panel.