grill
challenge assumptions, load product context
Explicit boundaries, data that does not lie, and systems you can explain.
Notes on AI engineering, data pipelines, platform tooling, software architecture, and SEO/AEO — practical deep-dives from production applications.
Tools and resources I rely on, organized by category — design, backend, AI, CI/CD, and more.
Not just today's stack — tools and patterns from years of projects and notes. Not a logo wall: a map of what I've used, still use, and would reach for again. Hover any entry to see the pattern behind it.
03
DDD, event-driven, legacy refactors, patterns that scale.
DDD, event-driven, legacy refactors, patterns that scale.
Domain-Driven Design
Code organized by feature & domain.
hover to inspect
modules/
billing/
workflows/
notifications/Event-Driven
DB triggers, queues, real-time processing.
emit('job.completed', { id, result });Result / Either
Explicit error types, no silent throws.
type Result<T> =
| { ok: true; value: T }
| { ok: false; error: E };Microservices
lio-api-serv-* decomposition — bridge, mailings, envíos, notifications.
// lio-api-serv-bridge
// lio-api-serv-mailings
// lio-api-serv-notificationsRPC-Only · Multi-Tenant
All DB access through Postgres functions with tenant isolation.
create function get_jobs(p_org uuid)
returns setof jobs
language sql security definer;Legacy Refactoring
Recovering complex codebases, monolith decomposition.
// before: 1 deploy · 1 DB
// after: api | worker | bridgecontext first · rules in the repo · human review
I don't chase better prompts — I chase better context. The agent writes; I lock product, constraints, and patterns before a single line ships.
challenge assumptions, load product context
lock constraints, patterns, and order
implement with repo rules and skills
review judgment, types, tests, ship-ready
2016 — 2017
Co-founder & Frontend Developer
Co-founded a small studio delivering responsive websites and email-marketing campaigns compatible with major email clients — my first step from freelance frontend work into building products end to end.
First end-to-end product ownership
2017 — 2019
Frontend → Full Stack Developer
Evolved from responsive frontend sites to full-stack ownership: maintained a custom CodeIgniter CMS, shipped a multi-domain page builder with centralized visual config and cross-domain content replication, and ran GSuite plus hosting-provider services.
Frontend to full stack in 18 months
2019 — 2022
Software Developer
Nearly three years on a single e-commerce marketplace product: migrated a performance-struggling monolith into microservices (central API, import server, task runner, payment/shipping/notification bridges), rebuilt UI/UX from scratch, and scaled from ~50 to ~1,000 concurrent users across infrastructure I built from zero.
~20× concurrent user growth
2022 — 2024
Software Developer
Worked with multidisciplinary teams on developing and integrating multiple products: enterprise Salesforce platform, D3.js newspaper-style chart MVP from a complex legacy refactor, i18n university CMS on Strapi, and mutual-fund calculator with GitHub Actions cron feeds and Sanity persistence. Led select builds with internal and external teams, plus formal CI/CD with ephemeral per-branch environments and contribution workflows.
Scaled team delivery without losing stability
2025 — Present
Backend Developer / Platform Engineer
I lead a workflow orchestration and notifications product while growing into team leadership: built push/email automation almost solo over ~11 months (Next.js 16 RSC, Supabase RPC-only backend, modular async engine), shipped NPM SDKs and a Firebase→relational correction — and today I mentor developers, define code starters, establish engineering standards, and run retros for the broader dev team.
Active product · mentorship, starters & team retros
2026 — ∞
Software Architect
Focused on software architecture leadership — open to roles where event-driven systems, applied AI, and clean platform design converge. Currently finishing Systems Engineering with a Computational Systems focus.
Open to software architecture & platform roles
Over a decade shipping products in production: from frontend to platform, Aerolab to Flywheel. Focused on product and architecture. Completing a Systems Engineering degree; production work did not wait for the diploma.
My approach: think about the product first, then choose architecture that fits. Maintainable, performant, honest code — no over-engineering, no abstractions for their own sake — just systems that solve real problems.
Open to new projects, technical challenges, and meaningful collaborations — whether you're a recruiter, founder, or fellow engineer.