Skip to main content

// the_real_problem

Hiring developers is a gamble.

Some write code that works.

Few understand WHY it should work.

Even fewer know WHEN that code shouldn't exist.

I'm not the dev who adds features.

I'm the one who asks if that feature should exist.

And then builds it in half the time.

// results > resumes

Wenalyze · 2024 - 2026

Two migrations. -70% latency.

"We need to migrate the backend."

"But we can't stop production."

"And it needs to be done yesterday."

We had outgrown Express. Firestore was slow and expensive for what we asked of it.

Before touching anything, I evaluated the options: an updated Express, FastAPI, NestJS.

I prepared architecture templates, prototyped the key modules and got the team on board.

First, the API to NestJS. Then, the database from Firestore to PostgreSQL.

Zero downtime. Zero broken features. No "we'll fix it later" moments.

Result: over 70% lower API response times.

Legacy code isn't scary. Letting it grow is.

  • TypeScript
  • NestJS
  • Express
  • PostgreSQL
  • Firestore
Wenalyze · 2024

-60% execution time

The scraping system had been running for years. Slow, expensive, fragile.

Nobody touched it because "if it ain't broke..."

I touched it. Not by adding code: by removing it.

Redundancies nobody saw. Flows that "had always been done this way".

Result: 60% less execution time and 30+ Open Data sources integrated.

Same data. Fewer resources. Lower AWS bills.

Sometimes the best code is the code you delete.

  • TypeScript
  • NestJS
  • PostgreSQL
  • Puppeteer
  • AWS
Wenalyze · 2024

Full product

Wenalyze Sync: from whiteboard idea to SaaS in production.

Expense management for companies: report an expense without keeping a single receipt.

Design, front end and API, from v1 to v2.

Everything, from first line to first user.

When someone says "from scratch", I hear "no excuses if something breaks".

  • Astro
  • React
  • TypeScript
  • ShadCN
  • Tailwind
  • Google Cloud
View project
Wenalyze · 2024 - 2026

Processes, not patches

A team of five doesn't need bureaucracy.

It just can't depend on anyone's memory.

I built the CI/CD pipelines with GitHub Actions.

I standardized the team's dev environment, removing friction before the migration.

I defined how we use LLMs for development, and kept iterating on it.

And I bridged the gap with Analytics and Marketing: APIs designed for their dashboards.

A good process goes unnoticed. You notice when it's missing.

  • GitHub Actions
  • CI/CD
  • Code reviews
  • Kanban

// tools

Tools are just tools. A hammer doesn't make you a carpenter. Knowing when NOT to use it does.

Missing something? I'll probably learn it before you finish typing the email.

// things_i_have_built

el-impostor

Real-time multiplayer game. On a Raspberry Pi. Because I can.

"Let's build a social deduction game like Among Us."

"Multiplayer."

"Real-time."

"And deploy it on a Raspberry Pi I have at home."

That's not a project. That's a personal dare.

WebSockets so everything happens instantly.

Clean Architecture because chaos doesn't scale (not even when it's 4 friends playing at 2am).

SSL because security isn't optional, not even on a Pi.

The best way to learn something is to build it when nobody asked you to.

  • React
  • TypeScript
  • Socket.io
  • Node.js
  • Supabase
  • Tailwind
GitHubDemo

wenalyze-sync

From "we need a dashboard" to SaaS in production.

Expense management for companies: report an expense without keeping a single receipt.

Sounds corporate. Sounds boring.

The interesting part is in the details:

- Architecture that optimizes API calls

- UI that doesn't need a manual

- Performance that doesn't make you wait

Design and front end, end to end; architecture, decided as a team.

Every screen, mine. Every 3am bug, too.

When the product has your name on it, there's nowhere to hide. And that's fine.

  • Astro
  • React
  • Next.js
  • TypeScript
  • ShadCN
  • Tailwind
Demo

gestió-renda

A complete ERP for tax-return season. In production. With real clients.

"We need to run the entire income-tax campaign."

An insurance brokerage. A season that explodes every April.

I built all of it. Solo. From scratch.

A state machine per return: booked → review → closed.

A calendar that catches appointment conflicts and lets you drag to reschedule.

DNI/NIE/CIF and IBAN mod-97 validation. CRM, audit log, billing.

14 tables. Bilingual. Command palette. Everything an office needs at 9am on a Tuesday.

There's no public demo. It holds real data from real clients.

The proof is the dossier. And the fact that the business runs on this every day.

No demo isn't an excuse. It's that someone trusted their whole operation to my code.

  • TypeScript
  • Next.js
  • React
  • PostgreSQL
  • Drizzle
  • NextAuth
Dossier

keku

A restaurant site the owner updates without calling me.

KEKU makes burgers with 50-day dry-aged beef.

I made sure their site lived up to it.

Interactive menu with an allergen system.

Reservations that land straight in the owner's WhatsApp.

An "open / closed" indicator that knows the KITCHEN hours, not the bar's.

But the important part you don't see:

The owner changes a dish or a price himself. No code. No phone call.

Bilingual, real SEO, from a design handoff to production.

The best product isn't the one that needs me. It's the one that doesn't anymore.

  • Next.js
  • React
  • TypeScript
  • Sanity
  • styled-components
Demo

What if this is what you need?

If you've made it this far, maybe we should talk.

Get to know me

// next_command

If you've made it this far, it's one of two things:

1. You have a project that needs someone who actually gets it.

2. You were bored and this was more entertaining than scrolling LinkedIn.

If it's the first one, let's talk.

If it's the second... thanks for reading, I guess.

LinkedIn

For those who prefer corporate protocol.

GitHub

For those who want to see code before talking.

// Alcàsser, València

// Remote, on-site or relocating: whatever makes more sense.

// Timezone: CET (but flexible if the project's worth it).

$ exit 0 // Thanks for scrolling this far.