Ramón Álvarez

Backend Engineer at Automation Labs · Maracaibo, VenezuelaGo · Python · JavaScript · C++. Ingeniero en Computación, Universidad Rafael Urdaneta (2022 – 2026), Cum Laude.

~/ralvarez.dev (main)$ cat about.md

01about

I'm Ramón Álvarez, a computer engineer from Maracaibo, Venezuela, building future solutions.I completed my computer engineering studies at Universidad Rafael Urdaneta, Cum Laude, and work remotely as a Backend Engineer at Automation Labs, where we build AI solutions for industry.I care about distributed systems, clean architecture and developer tooling, and I've led teams to national robotics competitions, designing the architecture, programming the robots and training their models.email:[email protected]github:github.com/ralvarezdevlinkedin:www.linkedin.com/in/ralvarezdev

~/ralvarez.dev (main)$ cat robotics.md

02robotics · team lead & main programmer

ORC 2025Lightning Boltline followers

WRO 2025Steel Botrobot Klevor

WRO 2026Voltimorrobot vTitan

Architecture, robot code, and model training. Qualified for nationals; not a win — the engineering is the point.

~/ralvarez.dev (main)$ cat facts.md

03facts

minecrafthosts Minecraft servers for friends, on my laptop, in Docker, with custom backups

gamingplays on Linux through Heroic; Fallout, The Last of Us, Uncharted

dailyFedora, GNOME, Zed, zsh

~/ralvarez.dev (main)$ ls -la ~/projects/

total 3drwxr-xr-xralvaskills2026-09-30go● active drwxr-xr-xvtitan2026-09-30python, go● active drwxr-xr-xklevor2026-09-30python● active

~/ralvarez.dev (main)$ cat thesis.md

04thesis

Distributed architecture with NATS for industrial telemetry.Hexagonal. OPC UA · Modbus · MQTT in,MCP · REST · gRPC out.

~/ralvarez.dev (main)$ ./diagram --illustrative

architectureillustrative architecture

  field bus           ⬡ application boundary · hexagonal             consumers        
                         inbound port ↓           outbound port ↑                     
  ┌───────────────┐   ┌┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┐   ┌───────────────┐
    ▸ OPC UA      ├─┐ ┆                                          ┆ └─┤ MCP            
  ├───────────────┤ │ ┆ ┌───────────┐ ┌──────────┐ ┌───────────┐ ┆ │ ├───────────────┤
    ▸ Modbus      ├─┼─┼ │           │─│          │─│           │ ┼─┼─┤ REST           
  ├───────────────┤ │ ┆ │  ADAPTER  │ │  DOMAIN  │ │  ADAPTER  │ ┆ │ ├───────────────┤
    ▸ MQTT        ├─┘ ┆ └─────│─────┘ └──────────┘ └─────│─────┘ ┆ ┌─┤ gRPC           
  └───────────────┘   ┆       │           NATS           │       ┆   └───────────────┘
                      ┆       └──────────────────────────┘       ┆                    
                      └┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┘

86 columns · 11 rows · scrolls sideways on narrow screens

Drag to orbit. Click, then scroll or pinch to zoom. Keys: arrows rotate, + and − zoom, 0 resets.

packets1.0×

nodes

Hover or focus a node to find it in the diagram. Press to keep it highlighted.

Illustrative architecture: hexagonal core on a NATS message bus

Three inbound protocols (OPC UA, Modbus, MQTT) connect to one inbound port.
The inbound port feeds the hexagonal core: an adapter, the domain, and a second adapter.
Both adapters are also connected to the NATS bus that runs beneath the core.
The core's second adapter leaves through one outbound port.
The outbound port feeds three consumers: MCP, REST and gRPC.

Nodes, roles and connections (illustrative)
Node	Role	What it is	Receives from	Sends to
OPC UA	driven adapter	Industrial protocol the core consumes.	none	Inbound port
Modbus	driven adapter	Industrial protocol the core consumes.	none	Inbound port
MQTT	driven adapter	Industrial protocol the core consumes.	none	Inbound port
Inbound port	port	One entry point. Every inbound protocol plugs in here.	OPC UA, Modbus, MQTT	Inbound adapter
Inbound adapter	adapter on the bus	Receives from the port; talks to the domain and to the NATS bus.	Inbound port	Domain, NATS
Domain	domain	The business logic. Knows nothing about protocols or transports.	Inbound adapter	Outbound adapter
Outbound adapter	adapter on the bus	Receives from the domain or the NATS bus; sends out through the port.	Domain, NATS	Outbound port
NATS	bus	The messaging backbone running beneath the core. Both adapters are clients of it.	Inbound adapter	Outbound adapter
Outbound port	port	One exit point. Every consumer is served from here.	Outbound adapter	MCP, REST, gRPC
MCP	driving adapter	One of three interfaces the data is exposed through.	Outbound port	none
REST	driving adapter	One of three interfaces the data is exposed through.	Outbound port	none
gRPC	driving adapter	One of three interfaces the data is exposed through.	Outbound port	none

~/ralvarez.dev (main)$ tail -n 3 ~/activity.log

2026-09-30rskcommit

2026-09-30vtitancommit

2026-09-30klevorcommit

~/ralvarez.dev (main)$ cat memoriam.md

05in memoriam

Javier Pérez @kaucrow 2005 – 2026 — my friend and classmate. Thank you for the years in the classroom and the countless hours debugging together. I carry your curiosity and your talent with me.Luna Margarita 2014 – 2026 — almost twelve years part of our family. Thank you for your company, your nobility and all the love you gave without asking for anything back.

~/ralvarez.dev (main)$