Uses

AI Tools

• Codex + Claude Code

  I use them for repetitive engineering work like boilerplate scaffolding, straightforward refactors, test skeletons, and doc cleanup. They reduce mechanical effort and speed up delivery, while architecture and final code decisions stay with me.

Editor & Terminal

• VS Code

  Primary editor for .NET, Next.js, and infra work. I keep the setup lean and rely on fast search and keyboard-driven navigation.

• macOS Terminal + zsh

  Most of my day runs in terminal tabs: build checks, git, deploy scripts, and quick debugging loops.

Languages & Frameworks

• C# / .NET 9

  My primary backend stack for APIs and enterprise workflows where reliability and maintainability matter.

• React + Next.js

  For fast, clean UIs that are easy to iterate on, especially for internal tools and operational dashboards.

• Python + Node.js

  Used when services or automation are better suited to lightweight microservices and scripting.

• Go (working knowledge)

  I have working knowledge of Go and I am actively building side projects focused on APIs, concurrency, and performance-oriented backend patterns as I move toward Go-focused backend roles.

Infra & Delivery

• AWS

  I ship to AWS and focus on production stability, observability, and straightforward rollback paths.

• GitHub Actions

  I prefer predictable pipelines and one-command releases over manual deploy checklists.

• Ansible + Terraform

  For repeatable environments and cleaner infrastructure changes, especially across multi-service projects.

• Prometheus + Grafana

  Monitoring that helps me catch regressions early instead of learning about them from users.

Debugging & Team Flow

• Postman

  Quick API validation during development and before handoffs to reduce avoidable integration bugs.

• Git + PR discipline

  Small commits, clean diffs, and direct PR descriptions. It keeps velocity high without sacrificing quality.

• Markdown docs

  I document deployment and troubleshooting paths while building so context does not get lost.

Hardware

• MacBook Air

  Light, quiet, and reliable. I optimize my setup around focus and low-friction context switching.

• Minimal desk setup

  I keep the desk intentionally simple so I can stay in flow longer with fewer distractions.

Off-Screen Co-Workers

Why cats?

They are part of my reset routine between deep work blocks. A few minutes with them helps me step away, clear context, and come back sharper for architecture and debugging decisions.

Building software is a long game, and the cats are a daily reminder to stay patient, consistent, and calm under pressure.