Tools & software
The editors, runtimes and command-line tools installed on my machine, and what each one is actually good for.
Last updated: September 2026
Editors
Two, because they are good at different things.
Terminal & shell
Where most of the work actually happens.
Orca ADE
Agentic development environmentCombines the terminal, git worktrees and coding agents in one place, so I can hand a well-scoped task to an agent in an isolated worktree and keep working in another.
Bash
Shell, lightly customizedNo Zsh, no framework, no plugin manager — a single ~/.bashrc I fully understand. The one real change is a two-line prompt: the working directory gets its own line in yellow, so a deep path never pushes what I am typing to the right edge of the screen.
# ~/.bashrc
if [ "$color_prompt" = yes ]; then
PS1='\[\033[01;33m\]>> \w\n${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[01;34m\]:\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\$ '
fiBrowsers
Zoho's privacy-focused browser. The reason I keep it is the built-in dark mode — unlike most extensions, it renders sensibly on almost every site rather than inverting colors and hoping.
Desktop
GNOME extensions I actually keep, out of the thirty or so I have tried.
The first four do the real work: tiling-assistant gives me keyboard window snapping, and no-titlebar-when-maximized buys back a full row of vertical space. The rest are small comforts — freon puts CPU temperature in the top bar, caffeine stops the screen blanking during a long build.
This collection changes as the setup does. Last updated September 2026.