Raúl Soto Nakao

01

Instant analysis with lots of data

The analysis tool fell short: few possible queries and slow screens when combining lots of data.

What changed

Controllers filter and combine data instantly, on maps and charts.

02

Test environments for the whole team

Testing a version depended on shared environments set up by hand.

What changed

Anyone on the team can start a complete environment, with known data, from a web page.

03

Reports without custom work

Every new report was custom work.

What changed

Reports are described and the system produces them.

04

Features without repeating the groundwork

Every new feature started by repeating the same structure.

What changed

The groundwork comes from the data model and the team focuses on what changes.

01

Analytics in the browser

Vue 3 · Crossfilter · DuckDB · D3.js

The server's analytics layer could not handle what was needed, so we moved part of the processing to the browser to widen the queries. With Crossfilter and DuckDB, filters, maps and charts stayed fluid, and the logic was kept separate so it could move to the server later.

The decision

Move the computation to the browser instead of waiting to scale the server, keeping the logic separate so it can move later.

02

Reproducible test environments

Docker · Docker Compose · Makefile · in-house web tool

On my own initiative: Docker images for each service, Docker Compose, known seed data, a Makefile as a common interface and a web tool to launch environments remotely, manage their containers and see each service's dependencies and status as a node flow.

The decision

A Makefile as a common interface, so every service starts the same way regardless of how it is built inside.

03

PDF reports with a custom language

TypeScript · custom DSL · PDF generation

A DSL to describe the documents and a generator that produces them.

The decision

Separate what the document says from how it is drawn: a new report is a description, not new code.

04

Base code generator

Node.js · Express · Vue 2 · MySQL

From the model's entities, the initial backend and frontend structure, configurable, so as not to repeat the same work for each feature. Another developer on the team used it too.

The decision

Configurable rather than fixed templates, so it would serve others and not just me.