Tools I Use in 2025

A snapshot of my current development setup — editors, terminal, CLI tools, and workflows.

August 15, 20252 min read

Editor

Neovim with a minimal config built on lazy.nvim. I've tried VS Code, Zed, and Cursor — they're all great, but nothing matches the speed of a well-configured Neovim for the kind of editing I do (SystemVerilog, Go, TypeScript across large codebases).

Key plugins:

  • telescope.nvim for fuzzy finding
  • nvim-lspconfig for language servers
  • nvim-treesitter for syntax highlighting
  • oil.nvim for file management

Terminal

Ghostty as the terminal emulator. It's fast, GPU-accelerated, and the configuration is dead simple. I switched from Alacritty last year and haven't looked back.

Shell is Zsh with a minimal prompt built on starship. No oh-my-zsh — just a handful of hand-picked plugins via zinit.

CLI Tools

The tools I reach for daily:

  • ripgrep (rg) — faster than grep, respects .gitignore
  • fd — better find
  • batcat with syntax highlighting
  • eza — modern ls
  • delta — better git diffs
  • jq / yq — JSON and YAML wrangling
  • hyperfine — benchmarking CLI commands
  • tokei — count lines of code by language

Version Control

Git with a set of aliases I've refined over years. I use git worktree heavily for reviewing PRs without stashing work. gh CLI for everything GitHub-related.

Languages & Runtimes

  • Go — my default for backend services and CLI tools
  • Rust — when performance is critical or I need zero-cost abstractions
  • TypeScript — anything web-facing
  • Python — scripting, ML experiments, EDA tool wrappers
  • SystemVerilog — hardware design (obviously)

What I've Stopped Using

  • Docker Desktop → replaced with colima + nerdctl
  • Postman → replaced with httpie and .http files in VS Code
  • Notion → replaced with plain Markdown files in a git repo

The trend is clear: I keep moving toward simpler, faster, text-based tools. The less abstraction between me and the work, the better.

toolsproductivityworkflow
Was this helpful?