AI lets me build workflows and environments I have wanted for years. I can finish in hours what used to take days, explore an idea without sinking a month into it, and review more code than I ever could alone.
That does not mean AI has solved software development. It has moved the bottleneck. Code is becoming cheap, but good ideas, clear requirements, architecture, communication, and judgment are not.
Instead of guessing what AI might become, let’s look at what it can actually do today. These are the projects and workflows I have completed with AI as of July 2026.
The short version is that AI is useful, but it is not magic. It is excellent at research, documentation, code review, scaffolding, testing, and shortening long debugging sessions. It is far less reliable when someone asks it to build complex software without understanding the system underneath.
Arch Linux has always been the distro for people who want control, speed, and the newest packages as soon as they land. That is also the tradeoff. When you live on the bleeding edge and pull from community package scripts, you are taking on more responsibility than most desktop Linux users realize.
The recent AUR malware incident is a good reminder of why I am looking at Fedora differently now. Fedora gives me modern packages, a strong default security posture, and a predictable release model without needing to trust random build scripts for everything I install.
DaVinci Resolve on Arch Linux is one of those setups that can be perfect for weeks and then break after one system update. The problem is not that Arch is bad or Resolve is bad. The problem is that Resolve is a proprietary professional video editor built and tested against a conservative Linux stack, while Arch is a rolling-release distribution that moves libraries, GPU drivers, and desktop components quickly.
This post goes through the common problems, the fixes that matter, and the workflow I use to make Resolve usable on Arch Linux.
Zed is what happens when an editor is built for speed first. It is written in Rust, rendered with the GPU, and feels instant in a way most Electron-based editors never do.
If you want VS Code comfort without Electron drag, Zed is a sharp middle ground that still delivers LSPs, Vim mode, terminals, Git, remote development, and AI.
Proper Linux benchmarking is not about the biggest single run. It is about building a clean baseline, controlling variables, repeating runs for statistical validity, and generating charts that show the data clearly.
The Phoronix Test Suite provides the structure: repeatable workloads, saved results, baseline comparison, and batch automation. MangoHud captures frame-time data. Together with a Python plotting tool, you get a complete workflow from raw test data to publication-ready charts.
Most editors today are bloated, slow, and pretending to be IDEs while burning your RAM. Neovim 0.12 goes the other direction: less junk, more control, better speed.
This is the no-BS breakdown of what changed in my Neovim setup, why I removed the old pieces, and what actually matters in daily use.
Brave Origin is Brave stripped back to what most of us actually want: fast browsing, strong privacy, and aggressive blocking. If you have ever opened a browser and thought, “Why is there a crypto wallet button, rewards UI, and extra services I never asked for?” this is the answer.
Most Linux users only run their package manager and call it a day. That updates your system packages, but it often leaves the rest of your machine in a partially updated state. If you use pip, cargo, flatpak, snap, brew, oh-my-zsh, VS Code extensions, or even dotfile repos, those pieces can all drift out of date separately.
Topgrade exists to solve this exact problem. It gives you one command to update almost everything you actually use.
Most people mount NFS shares with a short line and move on. That works, but if you use network storage heavily (media libraries, VMs, homelab backups, project files), your mount options directly affect reliability, boot behavior, and performance.
This guide breaks down a practical high-reliability NFS option set and compares it to a basic mount setup, using Linux nfs-utils mount documentation (man 5 nfs) and systemd mount behavior (man 5 systemd.mount).