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 - Present

Significant optimization

The scraping system had been running for years.

"It works" was the only requirement.

The problem: slow, expensive, fragile.

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

I touched it.

Not by adding code. By removing it.

Eliminating redundancies nobody saw.

Optimizing flows that "had always been done this way".

Result: significant reduction in execution time.

Same data. Fewer resources. Lower AWS bills.

Sometimes the best code is the code you delete.

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

Express to NestJS

"We need to migrate the backend."

"But we can't stop production."

"And it needs to be done yesterday."

I led the complete migration.

Zero downtime. Zero broken features.

No "we'll fix it later" moments.

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

  • TypeScript
  • NestJS
  • Express
  • PostgreSQL
Wenalyze · 2024

Full product

Wenalyze Sync: from whiteboard idea to SaaS in production.

Architecture. Frontend. API. Deployment.

Everything, from first line to first user.

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

  • Astro
  • React
  • TypeScript
  • ShadCN
  • Tailwind
View project

// 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.

A product for syncing enterprise data.

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

Designed and developed from scratch.

Every decision, mine. Every 3am bug, also mine.

When you have total ownership, there's nowhere to hide. And that's fine.

  • Astro
  • React
  • TypeScript
  • ShadCN
  • Tailwind
Demo

portfolio

The site where I say details matter.

Multilingual because València isn't just Spain.

Accessible because the web is for everyone.

100 on Lighthouse because green numbers are cool.

But mostly:

Because I wanted a place to say the things that don't fit on a one-page resume.

If a dev's portfolio isn't well made, why would you trust their code?

  • Astro
  • React
  • TypeScript
  • Tailwind
  • Motion
GitHubDemo

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.

// Alcasser, València

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

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

$ exit 0 // Thanks for scrolling this far.