Product engineering
Useful software shaped from the first ambiguous question through implementation, edge cases, and the release path.
UTC --:--
The signal / Partial self-portrait
Builder by instinct. Investigator by habit.
I am Joaquin. I like useful software, private systems, awkward edge cases, and the moment an experiment becomes something another person can actually use.
ACTIVE SIGNALA PERSON IS LARGER THAN THEIR OUTPUT
ORIGIN SIGNAL / UNFIXED
Curiosity is the common layer.
My work moves between product engineering, cybersecurity, infrastructure, and native applications. The surface changes; the underlying impulse does not: understand how the thing really works, then make it clearer, safer, or more useful.
Beyond software, I am drawn to photography, music, travel, 3D modelling, and the knowledge hiding just outside the current map. Learning is not preparation for the work. It is part of the work.
KNOWN TERRITORY / EXPANDING
The terrain changes. The impulse does not.
Security
Authorised research, defensive systems, identity, infrastructure boundaries, and evidence that survives scrutiny.
Systems
Native apps, web services, networks, cloud control planes, self-hosting, observability, and recovery.
WORKING CODE / THREE LINES
Trace the path. Preserve the truth. Leave a light.
- Trace
- Follow the real request through the interface, service, provider, device, and production boundary.
- Preserve
- Know which system owns the calculation, permission, or record—and do not quietly move that authority elsewhere.
- Illuminate
- Document enough that the next person can distinguish a map from a myth.
There is always another system worth understanding.
Open a channel ↗