Offline
A cash register can't wait for the Wi-Fi. Cut the network and keep selling.
0 sales queued0 sales synced
- No sales yet. Sell something.
Two-plus years with my hands on systems that move real money.
I don't lock myself into one stack: I adapt to whatever the problem needs and solve it creatively.
This is what I've built, and how I think about it.
My record, as a row that keeps getting updated.
2025 — now
Jan 2025 — present (1 year 10 months)
Creative Information Technologies (CIT)Current
UPDATE kevin
SET role = 'Associate Software Developer',
company = 'CIT'
WHERE since = '2025-01';2023 — 2024
Nov 2023 — Dec 2024 (1 year 2 months)
Asociación Hondureña de Maquiladores (AHM)
UPDATE kevin
SET role = 'Trainee Software Developer',
company = 'AHM'
WHERE since = '2023-11'
AND until = '2024-12';I'd rather show you how I think than tell you. Three real problems, shrunk down.
A cash register can't wait for the Wi-Fi. Cut the network and keep selling.
0 sales queued0 sales synced
An impatient customer taps Pay five times. They get charged once.
Idempotency key: ········
The first request charges. The rest get the same answer back.
An invoice is saved whole or not at all. If one line fails, nothing is left half-written.
In the database: nothing
My tools aren't a list: they're the layers a request travels through. Filter one and watch where it goes.
SELECT tool FROM kevin.stack;26 rows
How I work
Infra: everything runs inside
Client
Server
AI
Data
One project live and two slots reserved. The transaction is still open.
Live2026
A professional makeup artist's site: portfolio, services, catalog and local SEO in San Pedro Sula.
View projectView codeNext.js / React / GSAP / TypeScript

Pending
I'm building it. Check back soon.
Pending
I'm building it. Check back soon.