Open to full-time roles
Buenos Aires, Argentina

I build ideasin production.

Explicit boundaries and systems you can explain. No fluff.

Get in touchView timeline

Field notes from the build.

Notes on AI engineering, data pipelines, platform tooling, software architecture, and SEO/AEO — practical deep-dives from production applications.

Read note The Team Is the New Context Window
AI Engineering4 min
The Team Is the New Context Window

AI makes the individual developer faster, but not necessarily the team. Give ten developers the same tools and you get ten different ways of working, and that friction gets paid at the team level. The answer is not to make everyone work the same way, it is a shared base of rules, skills, and review criteria.

Read note
Read note When context starts working against you
AI Engineering5 min
When context starts working against you

An hour of Grill.me on a permissions system. I let the agent work and came back to a half-finished implementation: the context of that conversation had swollen and the original plan no longer fit. I dropped it into a file by phases, one new conversation per phase, and that is when it closed. ---

Read note
Read note Anti-Cliché: I used to spend more time fixing than writing
AI Engineering8 min
Anti-Cliché: I used to spend more time fixing than writing

I have used Cursor for a couple of years. I started on Tab. When I moved to agents, a chunk of my time went to reviewing and fixing what they generated. I built Anti-Cliché.

Read note
View all notes

What I've worked with.

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.

04

AI Agent Engineering

Spec-driven development, agent skills, MCP servers — applied AI in production, not just RAG.

  • Spec-Driven Development (SDD)

    Write the spec before the agent writes code — Grill.me interviews the plan until every branch is resolved, then a fresh agent builds against it.

    hover to inspect

    loc: 01.04sec: AI1
    # spec.md
## Requirements
## Acceptance criteria
// the agent implements against this, not vibes

  • Claude Code · Cursor

    Daily agentic coding — from Cursor's Tab autocomplete to full agent workflows with custom skills.

    loc: 02.04sec: AI2
    /anti-cliche  # custom skill, runs before every commit

  • MCP Servers

    Wiring agents to live data — this site's own content comes from a Sanity MCP server.

    loc: 03.04sec: AI3
    claude mcp add Sanity -t http https://mcp.sanity.io

  • Agent Skills · Multi-agent

    Grill.me-style multi-agent flows — one agent interviews the plan, another builds it.

    loc: 04.04sec: AI4
    phase-1.md → new conversation → phase-2.md
# context reset between phases

  • Context Engineering

    Splitting large plans into phases before context runs out mid-task.

    loc: 05.04sec: AI5
    # plan.md
## Phase 1: schema
## Phase 2: API
## Phase 3: UI

  • RAG · LangChain

    Semantic search over internal knowledge.

    loc: 06.04sec: AI6
    const docs = await retriever.invoke(question);
return llm.stream({ docs, question });

  • Vector Search

    Embeddings + pgvector for discovery.

    loc: 07.04sec: AI7
    select 1 - (embedding <=> $1) as score
order by score desc;

context first · rules in the repo · human review

I don't delegate thinking — I delegate implementation

I don't chase better prompts — I chase better context. The agent writes; I lock product, constraints, and patterns before a single line ships. Spec-driven development, not vibes.

how a task moves
0101 / 04

grill

challenge assumptions, load product context

agent: grillme
loc: 01.pipesec: GR
$ grill-me "agents section v2"
> why UI/UX, not just copy?
> what breaks if we skip it?
0202 / 04

plan

lock constraints, patterns — write the spec

agent: planner
loc: 02.pipesec: PL
$ writing-plans
✓ docs/specs/2026-09-03-pixel-scene.md
  4 steps · schema + query + component
0303 / 04

execute

implement with repo rules and skills

agent: engineer
loc: 03.pipesec: EX
$ read .agents/rules/ui/
✓ TDD: red → green → refactor
0404 / 04

verify

review judgment, types, tests, ship-ready

agent: reviewer
loc: 04.pipesec: VE
$ pnpm lint && pnpm typecheck
✓ 0 problems
// standbydebugger— diagnose + patch

Ten years, scrolled in sequence.

2016 — 2017

CoffeeCode

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

WordPressHTMLBootstrapjQueryJavaScript

2017 — 2019

Synapsis CI

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

PHPMySQLCodeIgniterBootstrapjQuerySCSSApachecPanel

2019 — 2022

Libre Opción

Full Stack Developer & DevOps

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 and DevOps I built from zero (Linux, SSL certificates, DNS/domains, Docker).

~20× concurrent user growth

Nuxt.jsReactPHPSlimJWTMercadoPagoFirebasePythonMariaDBApacheAWSDocker

2022 — 2024

Aerolab

Full Stack Developer

Worked with multidisciplinary teams on developing and integrating multiple products, including an enterprise Salesforce platform, a D3.js newspaper-style chart MVP from a complex legacy refactor, an i18n university CMS on Strapi, a mutual-fund calculator with GitHub Actions cron feeds and Sanity persistence, and an internal monitoring tool with scraping, AI, and cron jobs integrated with GitHub and Notion. 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

Next.jsNode.jsTypeScriptSalesforceStrapiSanityD3.jsPrismaOpenAITurborepoDockerPostgreSQLGitHub Actions

2025 — Present

Flywheel Studio

Senior Full Stack Developer & Mentor

I lead an internal product for large-scale workflow orchestration and notifications with multiple external integrators, built from the ground up (Next.js RSC, Supabase RPC-only backend, modular async engine). I also contribute to another internal product with multi-LLM orchestration via the Vercel AI SDK and a RAG pipeline on pgvector. I implemented the CI/CD pipeline, automating deploys and PR reviews, and published npm SDKs alongside a Firebase→relational migration. Today I mentor developers, define code starters, establish engineering standards, and run team retros.

Active product · mentorship, starters & team retros

TypeScriptNode.jsPythonNext.jsAI SDKRAGDenoSupabasePostgreSQLFirebaseSanityStripe

2026 — ∞

Next

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 Full Stack, Mentor, Architecture, Platform, and Applied AI roles

ArchitectureSystem DesignAI ToolingCloud NativeOpen Source

A few stories from my career.

Real situations I lived through, the problem, the call I made, and why.

From a Monolith to a Distributed Architecture, Without Rewriting the Product

A monolith stopped working once modules with very different needs began competing for the same infrastructure. I migrated responsibilities into microservices without rewriting the product or stopping development.

Impact

~10 microservices, zero rewrite

When the Platform Had to Handle 20× More Traffic

When demand spiked far beyond what our monolithic backend could handle, we didn't rewrite the infrastructure — we distributed traffic across instances and multiplied capacity by 20×.

Impact

~20× more user capacity

Designing a Process That Didn't Depend on an Unreliable Product Owner

When a client's temporary product owner couldn't manage requirements, we didn't try to fix the person — we redesigned the process around them.

Impact

On-time delivery, zero contract slippage

View all
portrait_01.jpg
Endev
About

How I build and why

If you made it this far, you probably want to know a bit more about me. I've spent many years building software, and what matters to me hasn't changed since the beginning, watching an idea turn into something that actually works.

Code is only part of the job. Some days it's product thinking, other days architecture, watching a deploy, or staying a little longer to figure out why something that worked yesterday stopped working today. That's production. It has a personality of its own.

I also enjoy helping others grow. A good code review doesn't just point out what's wrong, it leaves the other person understanding something they didn't before.

I care about understanding the problem, discussing decisions when they matter, and finding the simplest, most solid way to ship to production.

I work mainly with TypeScript and Node.js, and keep a close eye on AI and agents because the work is changing fast. I adopt new tools when they genuinely improve the product, the team, or how we work.

I'm finishing a Systems Engineering degree, though my career didn't wait for the diploma. Most of what I know I learned by building and getting things wrong on real systems.

  • Frontend and backend
  • Architecture and standards
  • Mentoring
  • Next.js
  • AI-assisted engineering

Get in touch

Open to new projects, technical challenges, and meaningful collaborations -- whether you are a recruiter, founder, or fellow engineer. Write through the form or email the address on this page. I work from Buenos Aires (GMT-3) and reply in English or Spanish.

Availablebuenos aires
Local time--:--
StatusOnline

Usually replies quickly

Name

Email

Message

Your information stays private and is never shared.

Curriculum vitae
HTMLPDF