Eduardo Simon

Eduardo Simon is a software engineer working across application development, cloud infrastructure, and AI-assisted engineering workflows. Based in Valencia, Spain, he builds React frontends, backend services, and AWS infrastructure at Flywire. His public projects and technical proposals address practical ways to make shared engineering conventions easier to follow.

Making engineering conventions usable

In March 2020, Eduardo requested support for custom code generators in the NestJS command-line tool. His team used an event-sourcing library with recurring structures for commands, event handlers, and view updaters. He wanted engineers to generate those structures through the CLI they already knew. The proposal connected architectural consistency to a concrete developer experience: following the team's conventions should not require learning a separate tool.

His public projects address application development and infrastructure tooling:

• Collaborative budgeting: budget.io imports bank transactions through GoCardless and organizes spending into categories with monthly allocations and funding targets. It brings transaction ingestion and shared budget planning into one application.
• A simpler AWS command line: aws-ug-cli is a demonstration tool written in Go with Cobra. It separates command arguments, service logic, and AWS clients. Interfaces around the clients let the service code be tested without requiring each test to call AWS.

Model reasoning inside reviewed workflows

Eduardo and Javier Casal jointly describe Orbit, Flywire's internal platform for AI-assisted engineering workflows. Their approach places model reasoning inside a process whose predictable steps remain ordinary code. Workflow definitions live in YAML, pass through merge-request review, and specify the tools and access available to each step. The platform runs on Flywire's existing deployment infrastructure.

The code-review workflow makes that design concrete: the model can inspect code but cannot modify it. Eduardo and Javier report more than 9,700 code-review runs in 30 days, while human merge-request review remains part of the process. Other applications include translation updates, dependency fixes, ticket triage, and changes across repositories.

There is a practical connection between Eduardo's earlier generator proposal and the workflow approach he describes with Javier: both make a shared engineering practice available through tools and processes a team already uses. The NestJS proposal would put recurring code structures inside a familiar CLI; Orbit puts model-assisted tasks inside reviewed workflows. That connection concerns how engineers adopt the tools, without assigning Eduardo sole authorship of the platform.