My daily development setup looks very different from the one I used to rely on. I open Herdr, a terminal workspace manager, keep one or two tabs for coding agents, and use a third for Neovim, my text editor. That arrangement has completely replaced VS Code and Cursor in my day-to-day development.
Omarchy was the turning point, and the changes grew beyond that first setup. Terminal tools, a familiar workspace across machines, touch typing, and even dictation have all made it easier to keep moving without breaking my flow.
I wanted to share this reflection because I care a lot about having a clean development environment with as little friction as possible. I wish I had discovered this way of working earlier in my career. Small interruptions add up when you spend your day developing software, and finding a setup that helps me stay focused has made a difference I want other people to experience too.
Back to the terminal
My relationship with the terminal developed gradually. When I was working with drones, I first connected over SSH from a terminal. Later, I used VS Code for that work. Along the way, I became familiar with VPNs such as ZeroTier and eventually got comfortable using SSH keys.
Those tools became part of how I reached the machine I needed to work on. Over time, something that initially required deliberate attention became ordinary.
My current setup feels like another step in that progression. I am spending more of my day in the terminal again, now with tools that make editing, reviewing changes, and managing the development environment feel connected.
Omarchy was the turning point
For me, the value of Omarchy has been the combination of preconfiguration and exposure. Having a working environment in front of me made it easier to try tools I might otherwise have kept putting off.
Omarchy’s development tools documentation covers its editor choices, Docker tooling, and Git tools. But the part I want to recommend comes from using the setup every day: the tools began to feel like they belonged together.
I did not have to decide on an entire ideal workflow before getting started. Using the environment helped me discover what I wanted to keep. LazyVim, Lazygit, and Lazydocker became natural extensions of my daily work.
A workspace that keeps the work together
Herdr gives me a terminal workspace for the arrangement I now use: one or two agent tabs and Neovim in the third.
The agents are close to the place where I read and edit the code. I can move between them while keeping the project in view.
Herdr also makes it handy to keep track of multiple projects at once. I can organize them into separate workspaces, each with its own tabs, and switch to the project that needs my attention. I do not need to spread every project across another set of windows or keep every terminal visible. The work stays accessible while the screen stays manageable.
LazyVim is the Neovim configuration that made this editor part of my daily work. Lazygit and Lazydocker extend that same feeling to Git and containers.
Their value to me is how naturally they fit into the work. Editing code, dealing with repository changes, and checking containers no longer feel like separate destinations. They are things I can move through while keeping the task in my head.
I feel faster with this setup. I have not measured that as a productivity benchmark; what I notice is less friction and fewer interruptions to my concentration.
The workflow travels with me
Herdr’s remote access over SSH extends this way of working to other machines. I use it to carry my development practices into the machines I connect to for server deployments or robot control.
The machine changes, but the workspace structure stays familiar. I can keep using the same approach to organizing terminals, agents, and editing while working where the code or hardware actually lives.
It brings me back to SSHing into drones, now with a workspace that feels continuous with my everyday development setup.
I brought parts of this workflow to my MacBook too. It is not running Omarchy, but the tools and habits I discovered through Omarchy still make my daily work feel smoother there.
That is one of the strongest reasons I recommend giving it a try. The benefit has extended beyond the machine where I first used it. The preconfiguration gave me a starting point, and exposure to the tools changed what I reached for elsewhere.
Getting ideas into the computer
The environment is only part of the experience. I also changed how I enter text, whether I am making a precise edit or trying to capture an unfinished idea.
Becoming comfortable with the keyboard
I used to think learning to touch type was overrated. Getting comfortable enough with the keyboard to know where every key was seemed like a lot of effort for a modest benefit.
Now it feels essential to how I work.
As more of my workflow moved onto the keyboard, that comfort became more valuable. I could give more attention to what I was trying to do and less to entering it. For me, it has become a productivity boost that supports all the other tools.
I would keep this advice simple: if you are spending much of your day typing, give yourself the chance to become comfortable with it. I underestimated how much that comfort would matter.
Sometimes speaking is the easier way to start
Voxtype and Wispr Flow have also become useful ways to get ideas into text.
I still feel a little cringe using dictation. Speaking an unfinished thought out loud can feel awkward. Even so, it helps me get ideas out and turn them into clearer notes and prompts.
Touch typing and dictation serve different moments for me. The keyboard is comfortable when I know what I want to write or need to make precise edits. Speaking can help when the idea is still forming and I want to get it out before trying to organize it.
The rough text gives me something to work with. I can then read it, clarify it, and decide what I actually meant.
What I would recommend trying
I would recommend trying Omarchy and giving its tools enough time to become familiar. For me, it has represented a real before and after in daily development.
You can also start with one part of the workflow on your current machine. Try LazyVim, use Lazygit for your regular Git work, or bring Lazydocker into your container workflow. If you work with terminal agents, try keeping them alongside your editor in Herdr.
Choose something you already do every day. That gives you a real task through which to learn the tool and decide whether it makes the work feel better.
For me, this setup is hard to go back from. The tools keep my projects and machines manageable, while typing and dictation make it easier to put thoughts into words. Together, they help me stay with the work.
If you try one part of it, pay attention to how it feels during an ordinary development session. That is where the difference became clear to me.