Skip to content

my kitchen

Uses.

Everything I reach for when I am cooking software. Not a flex, not a prescription — just the stuff that keeps me shipping.

the stack

Tools of the trade

Language & Framework

PythonVue.jsTypeScriptJavaScriptNode.jsNuxt

Data & Backend

Python servicesREST APIsData pipelinespandasPostgreSQLSQLite

Index tooling

Index managementRebalancingConstituent dataWeight calculationsAutomation

Frontend & UI

Vue 3ViteTailwind CSSModern CSSAccessibility

Tooling & Deploy

GitCI/CDDockerCloudflare PagesGitHub Actions

AI-augmented dev

ClaudeopencodePI agentDeepSeekKimiMCP

the setup

Around the desk

Editor & terminal

  • VS Code

    Home base. Vue/Volar tooling, integrated terminal, and a keybinding for everything.

  • JetBrains Mono / Space Mono

    Ligatures on, always.

  • Windows Terminal + PowerShell

    On Windows. Tabs, panes, and a theme that does not hurt.

Operating systems

  • Fedora KDE

    Daily driver for development — fast, clean, and always current.

  • Windows

    For everything else, and the occasional corporate tool.

  • Dual-boot

    Two operating systems, one reboot away from regret.

AI in the kitchen

  • Claude

    Primary pair-programmer — refactors, tricky logic, and rubber-ducking architecture.

  • opencode

    Terminal-native agent for multi-file changes without leaving the shell.

  • PI agent

    Agentic flows that switch between Claude, DeepSeek, and Kimi depending on the job.

  • DeepSeek

    Sharp reasoning, cheap tokens — great for the long tail.

  • Kimi

    Long-context model for chewing through big files and logs.

Browser & DevTools

  • Chrome / Edge DevTools

    The Network tab is where mysteries get solved.

  • Responsive mode

    If it breaks at 360px, it is broken.

  • Lighthouse

    For the performance guilt trip.

Hardware

  • Mechanical keyboard

    Loud enough to annoy the bugs.

  • Two monitors

    One for the code, one for the docs.

  • A decent chair

    The real performance upgrade.

on the horizon

What I'm watching

The part of the job that seems to change every few months. These are the things I am reading about, poking at, and slowly forming opinions on.

Agent fleets, not copilots

Coordinators that delegate to many subagents working in parallel — the shift from "autocomplete" to directing a team. Human reviews, not types.

MCP everywhere

The Model Context Protocol is turning agents into real tools with access to repos, databases, and browsers — plus guardrails that decide which tool may run when.

Agentic engineering

Structured plan → implement → test workflows with review gates are replacing free-form vibe coding. Process, not just prompts.

Long-running cloud agents

Agents that keep working when your laptop is closed, carrying shared context across sessions and machines.

Local & on-device models

Capable models running on your own hardware — private by default, and fast enough to be useful.

The one true tool

None of the above matters as much as this: ship it, look at it, fix it, ship it again. Tools are just the pan — the cooking is on you.

// hidden dev joke