About
Engineering as a discipline, not a trade
I'm a full-stack software engineer with over 6 years of experience designing, implementing, and optimizing distributed systems for payments, bank integrations, data pipelines, and SaaS products. I started in 2020 building internal dashboards and PHP websites, and since then I've worked across regulated fintech, operational logistics, and my own products end to end.
I specialize in backend architecture, API design, and real-time integrations, combining engineering reliability with business scalability in fintech and data-intensive products. That backend foundation is complemented by hands-on experience in logistics (routing, geospatial tracking), native Android development (Kotlin + Jetpack Compose), and browser extension engineering, so I can design a complete system without depending on someone else to cover half the stack.
I'm currently founder and CTO of two companies: Soluti, a logistics distribution center in Colombia, and Agendity, a scheduling SaaS for salons and barbershops. In parallel, I still work as an engineer inside other companies' teams (bank integrations in fintech, e-commerce with complex payments). That combination of roles, founder and also engineer inside a team, is intentional: it keeps me honest about which architecture decisions are actually necessary and which are just preference.
Outside client work and my own companies, I keep a steady pace of personal projects: automation, connectors to third-party systems, browser extensions, data pipelines. I don't build them on assignment, I build them because solving that kind of problem is simply what I enjoy most about this craft. Several of the blog's topics come directly from there.
I work from Medellín, Colombia, in a timezone that overlaps several hours a day with the US and much of Europe, which makes live coordination simple even with fully remote teams.
How I think about engineering
Code as craft
I treat code as a long-term asset; it should be readable, predictable, and able to evolve gracefully.
Always asking why
I favor architecture that scales naturally over the quick fix that accumulates technical debt.
Clean and intentional design
I apply SOLID, DRY, and clean architecture to keep systems decoupled, testable, and easy to reason about.
Maintainability as real speed
Sustainable velocity comes from clarity, testing, and smart abstractions, not from rushed complexity.
Quality built in
Testing, observability, and documentation are part of the delivery cycle, not an afterthought.
Full ownership
I see every feature as an engineering commitment that must perform, recover, and communicate clearly.
Default stack
The problem decides the tool.
Education
Systems Engineering
Universidad Simón Bolívar, Barranquilla
2018 to 2023
Certifications & courses
- Web Security Essentials
- Microservices Architecture
- Cloud Computing (AWS & Azure)
- Docker & CI/CD Pipelines
- Clean Code Practices
- Advanced Git and Version Control