I was wrong btw

2025-07-03 · Source: ThePrimeagen · Field: Technology & Digital — Software Development & Engineering · Depth: Intermediate, long

Summary

A developer details his transition to Arch Linux, driven by a philosophy of optimizing developer experience rather than aesthetics or novelty. He outlines his "tilos of rice" in four steps: prioritizing defaults, minimizing visual searching, avoiding new tools without real reason, and creating tools for experience improvement, not just keystroke savings. His setup features Hyperland as the window manager, a custom Waybar displaying server status and minimal time details, and a focus on keybinding efficiency using "super" as the modifier. He leverages tools like Ghosty Plus T-Mox, Vim with LSP navigation (GD, Shift K, Leader Dr. RR), Harpoon for file jumping, and Telescope for fuzzy finding, all aimed at streamlining navigation and reducing mental overhead in daily coding tasks.

Key takeaway

For software engineers seeking to optimize their daily workflow, prioritize reducing mental cycles over merely saving keystrokes. Focus your customization efforts on streamlining navigation within your window manager, browser, and editor, ensuring instant access to programs and files. By embracing sensible defaults and minimizing unnecessary configuration, you can free up cognitive resources for problem-solving, transforming repetitive tasks into effortless actions and significantly enhancing your overall developer experience.

Key insights

Optimize developer experience by minimizing mental cycles through efficient navigation and adherence to sensible defaults.

Principles

• Prioritize system defaults to reduce configuration overhead.
• Optimize for single-key navigation over visual searching.
• Avoid new tools without a clear, functional reason.

In practice

• Configure Waybar for essential system/server status indicators.
• Map workspaces to specific applications for instant access.
• Utilize LSP, Harpoon, and Telescope for rapid editor navigation.

Topics

• Arch Linux
• Developer Experience
• Hyperland
• Vim
• LSP Navigation
• Workspace Management
• T-Mux

Best for: Software Engineer, Machine Learning Engineer

Related on AIssential

• Optimizing Your IDE for Metadata-Driven Data Engineering — Fragmented data engineering tooling reduces productivity, especially in MDDE, necessitating an integrated IDE solution.
• ScreenSearch: Uncertainty-Aware OS Exploration — Effective GUI exploration requires balancing screen novelty with ambiguity reduction to navigate partial observability.
• A Peaceful Morning + Programming: The Productivity Hack No One Talks About — Uninterrupted morning focus significantly enhances programmer productivity and problem-solving by reducing cognitive load.
• Pinterest Engineers Eliminate CPU Zombies to Resolve Production Bottlenecks — Unused default agents can leak kernel state, causing hidden CPU bottlenecks and system instability.
• I Stopped Chasing AI Hype and Started Building Systems That Actually Worked — Focus on practical problem-solving and friction removal to build effective AI systems, not just advanced features.
• Do LLMs Benefit From Their Own Words? — LLMs often do not benefit from their own prior responses, and omitting them can improve quality and reduce context length.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by ThePrimeagen.