My Development Workflow in 2025

Oct 1, 2025 · 6 min read

WorkflowProductivityToolingTypeScript

Over the last few years, my dev setup has converged into something I'm genuinely happy with. Here's the full stack of tools and practices I use daily.

Editor & Terminal

  • Neovim with LSP for TypeScript, Go, Ruby, and Python
  • tmux for session persistence across work trees
  • kitty terminal for GPU-accelerated rendering
  • zsh with custom completions

I switched from VS Code to Neovim in 2023 and haven't looked back. The key wasn't speed — it was the modal editing model for structured navigation.

Project Structure

For every project, I enforce a consistent directory layout:

This hexagonal-style separation means I can swap frameworks without rewriting business logic.

CI/CD

  • GitHub Actions for CI
  • Biome for linting and formatting (replaced ESLint + Prettier)
  • Husky + lint-staged for pre-commit checks
  • Docker for production builds

The single biggest time saver was consolidating linting into Biome. Having formatting, linting, and import sorting in one tool with sub-second execution was a quality-of-life improvement I didn't expect.

AI in My Workflow

  • Claude / Cursor for code generation and refactoring
  • Supabase Edge Functions for serverless AI inference
  • OpenAI embeddings for semantic search features

The pragmatic approach: AI for implementation detail, not architecture decisions. The machine writes the code; I design the system.

The Principle That Changed Everything

"Make it correct, make it clear, make it concise, make it fast — in that order."

I used to optimize for speed too early. Now I write the clearest possible version first, then profile and optimize only the hot paths. The result: fewer bugs, easier reviews, and production code that's genuinely maintainable.