From the database to the interface

A place for your coding agents to work that is not your machine. Name a task and hort sets up an isolated box for it, with your code on a branch of its own: the agent runs freely inside, and your machine stays untouched. The box stays up when you leave, like a tmux session, so several agents work side by side and you walk back into any of them whenever you want.

            $ hort up fix-loginworktree   fix-login          readycontainer  box-fix-login      runningmounted    /workdir
          

Year

2026

Role

Author

The design: several people edit the same map at once, the work continues offline and merges on reconnect, and on geometry that carries legal weight the server does not resolve a conflict on its own: both versions are kept and a person decides. Built so far: the sync server in Django and PostGIS, with its tests and CI, and a logic core in Rust compiled to WebAssembly and wired into the Angular client.

Year

2026

Role

Author

Fifteen service landing pages, each with its own funnel, over a hub of three areas. A headless CMS so the marketing team publishes without a deploy, server-side rendering on every route, dynamic meta tags and Schema.org JSON-LD. Underneath it, a design system of 44 components on CVA and Signals, unit coverage above 80% on business logic, and Playwright over the critical flows.

Year

2026

Role

Developer

Business rules in C# 12 on a hexagonal architecture, with the domain, application and infrastructure layers kept strictly apart. ASP.NET Core 8 and EF Core 8 over PostgreSQL with PostGIS for the spatial joins, Redis for distributed caching of external lookups, Polly for retry on the government APIs, and QuestPDF for reports that carry a cryptographic hash so they can be audited. Over a hundred mapped functional requirements, under Central Bank rules for rural credit. Tested with xUnit, Moq and FluentAssertions.

An internal system under confidentiality: no source and no client names. I wrote a large part of it as one of four developers, and the architecture and decisions can be discussed in an interview.

Year

2025

Role

Backend engineer, team of four

Four working surfaces: a comparative viewer for six indices (NDVI, EVI, NBR, NDWI, NDMI and SAR/RVI) across two periods plus a difference map; a query builder against the European Space Agency Copernicus openEO platform from the property polygon; an automatic crossing of the property perimeter against nine mandatory public sources, from PRODES and DETER to CAR, SIGEF and indigenous land; and a consolidated workspace with a risk traffic light and a PDF export. Thresholds are calibrated per Brazilian biome, and every report carries a SHA-256 hash, source timestamps and full data provenance, which is what makes it usable in a legal process.

Screens are shown redacted. It runs on client property data.

Year

2025

Role

Author

When a contract is signed, the CRM sends the client data to n8n, which does the rest: a ClickUp folder with the standard task list (discovery, design, development and the rest), deadlines that move as the project moves, and a Google Drive folder with every document that matters. The ClickUp API does not expose the public link of a board, so a Puppeteer script logs in, switches the link on and hands it back to n8n, which puts the access details in the welcome email. Built at Valkeer, the agency where I worked as a fullstack developer.

Role

Developer

It captures one audio stream per participant rather than one for the room, which is what removes the usual speaker identification problem: who said what is known, not inferred. The pipeline runs recording, Opus encoding through FFmpeg, transcription and analysis on Gemini 2.5 Flash, and returns a Markdown report with the transcript, the summary, the decisions and the action items. Tone and level of detail are parameters.

Year

2025

Role

Author

Practice areas, the team, the history of the office, a blog for legal articles, and direct conversion through WhatsApp, phone and a contact form. Responsive, image optimised, with local SEO set up for search around Barretos.

Role

Developer

A farmer needs money now and is only paid at harvest. The instrument that bridges that gap in Brazil is the CPR, a rural product note. Lavra runs its whole life: the document as an immutable record, the georeferenced collateral, the payment schedule, the balance corrected by an index, and every event from settlement to default. Most of that runs in a spreadsheet today.

Year

2026

Role

Author

A study project: Django templates, models and forms over a vehicle catalogue.

Role

Author

Built to practise composing small components into larger behaviour rather than to ship a product.

Role

Author