Skip to content

Portfolio

This section turns Dionisio Developer work into more than a showcase.

The goal here is to show projects with context:

  • what problem the product solves
  • how the experience is organized
  • which technical choices matter most
  • where the most interesting trade-offs live

It is a portfolio built for people who want to understand the work and learn from it at the same time.

How to read it with a product and engineering lens

Section titled “How to read it with a product and engineering lens”

Instead of looking only at interface or stack, pay attention to:

  1. the core promise of the product
  2. where experience clarity matters most
  3. what kind of architecture likely supports the delivery
  4. which decisions seem driven by cost, speed, or simplicity
  5. what you would keep or change

That kind of reading turns a portfolio into usable range.

A 1v1 real-time competitive coding game with an authoritative server, Elo matchmaking, and bots.

Code Royale preview

What to observe:

  • authoritative state over WebSocket, and what the client is allowed to predict
  • a countdown that stays correct across reconnects and background tabs
  • matchmaking that widens its window and falls back to a bot instead of leaving a dead queue
  • per-topic Elo: one identity, many ladders
  • a challenge bank treated as a correctness problem, not just a content one

A real-time data product with update pressure, fast consumption needs, and backend thinking at the center.

SportPulse.today preview

What to observe:

  • information aggregation and organization
  • clarity for quick consumption
  • modular backend thinking with practical focus
  • the role of performance in a product that depends on freshness

A strong case for guided flow, multi-step progression, and perceived value built through results.

Amorfy preview

What to observe:

  • step progression
  • long-form UX
  • interface copy
  • turning answers into a strong sense of value

A direct tool with a clear primary action, readable feedback, and product expansion potential.

Wheel Of List preview

What to observe:

  • frictionless entry
  • immediate visual feedback
  • state management
  • extending a lean utility into a broader product ecosystem

Taken together, these projects show a recognizable approach:

  • clear product usefulness
  • simple but intentional experience design
  • enough engineering depth to support real use
  • clarity before unnecessary complexity

That combination also shapes the rest of the site.

To see real-time state, time, and trust under pressure

Section titled “To see real-time state, time, and trust under pressure”

Start with Code Royale.

To see backend, updates, and data in context

Section titled “To see backend, updates, and data in context”

Start with SportPulse.today.

Start with Amorfy.

To study utility, focus, and direct interaction

Section titled “To study utility, focus, and direct interaction”

Start with Wheel Of List.

  • Go back to the Blog to connect the projects with technical perspective and positioning
  • Open the Reference when you want stronger fundamentals for interpreting the decisions
  • Use the Resume material to turn work into proof of value