uses

A curated list of the hardware, tools, and stack that power my daily work. 💚 marks favorites.

💻 hardware

• macbook pro m4 pro — Apple Silicon, the whole workday on one charge.
• macos · linux — macOS on the laptop; Linux on every server, container, and CI runner.

⚡ terminal

• ghostty 💚 — fast, native, zero fuss. The whole day happens here.
• tmux — sessions and panes that survive anything.
• fish — auto-suggestions and highlighting out of the box.

🛠️ editor

• neovim 💚 — main editor. LSP-configured for Python, Clojure, and Ruby.
• zed — second editor, reserved for a handful of very specific jobs.

🚀 cli & tooling

• just 💚 — command runner; a justfile in every project, including this site.
• zola — Rust static site generator. Builds what you're reading in milliseconds.
• git — plain CLI, the occasional TUI when a rebase gets gnarly.

💚 languages

• python 💚 — my default for backend work. Eight-plus years in production.
• clojure 💚 — three years of financial systems at QuintoAndar. Immutability pays at audit time.
• ruby (rails) — current rotation at Solvis.
• java (spring) — the language I trust on a 10-year-old codebase.
• rust 💚 — what I'm studying right now. My toolchain keeps turning Rust, and this site is built by it.

🧩 frameworks

• django ninja 💚 — typed, Pydantic-first REST. Where new Django work goes.
• flask — smaller services and integration glue.
• fastapi — async services and typed APIs.
• spring — Java's REST workhorse, scaled out on FinancePlatform.
• past: django rest framework — carried the Olist and Agriness APIs for years.

🗄️ data & messaging

• postgresql 💚 — boring, correct, predictable. Exactly what a database should be.
• mysql — still a fine database when chosen for the right reasons.
• datomic — immutable, time-travel queries. The perfect store for financial entries.
• kafka 💚 — async backbone at Agriness. Decoupling done right.
• rabbitmq — queues, routing, and background jobs. Tasks to deliver, not streams to replay.

☁️ cloud & infra

• aws 💚 — primary cloud since the Olist Heroku → AWS migration.
• gcp — the second cloud in the rotation. Same principles, different console.
• kubernetes — led the migration into it at Olist; lived with it ever since.
• docker — same images everywhere: local, CI, production.
• past: heroku — where Olist started. Migrated away for cost and control.

🔁 ci/cd

• gitlab ci/cd 💚 — YAML-first, easy to reason about, batteries included.
• github actions — same idea, different ecosystem, nicer marketplace.
• pytest — fixtures, parametrize, plugins. Everything a serious backend needs.

💡 philosophy

• Boring where it matters. Postgres, Django, Spring — tools that outlive frameworks.
• Decouple early. Kafka and clean interfaces beat heroic refactors three years later.
• Test what breaks. Automated tests on the seams: integrations, queues, financial entries.
• CI/CD by default. Every project ships through pipelines from day one.
• Clean code is a courtesy. The next engineer is usually me, six months from now.

last updated: july 2026