The Workflow That Made Claude Code Actually Useful
I started vibe coding and it didn't get me where I wanted. Here's what I changed.
May 20, 2025
Cloud Architect & Enterprise Solutions Leader
Based in Honduras · Working globally
10 years delivering mission-critical financial systems in regulated environments — translating complex business requirements into reliable Azure-based solutions, and leading the teams that ship them.
Explore my work ↓YEARS
0+
years · Enterprise financial systems
DOWNTIME
0%
Downtime reduction
CERTIFICATIONS
0
Cloud certifications
Selected Work
Led migration of a mission-critical financial platform to a distributed Azure HA architecture — translating business continuity requirements into delivery plans and full infrastructure automation with Terraform and ARM.
95% reduction in downtime. Stable, repeatable deployments.
Led the architecture decision-making behind a full platform migration, framing the choice around governance maturity, ecosystem alignment, and long-term cost position — not just a technical comparison.
Strategic direction adopted at leadership level. Converted into a funded implementation program.
Designed an Azure microservices platform integrating AKS, API Management, and private endpoints for scalable, secure enterprise service delivery in a regulated financial environment.
Scalable, secure architecture supporting continued business growth.
Partnered with product and business teams to decompose a monolithic core financial application into modules and expose its capabilities via APIs.
Improved data accessibility, system reliability, and delivery speed for every dependent team.
Re-engineered Azure DevOps pipelines for .NET, Angular, and React teams — creating reusable YAML templates and automated quality gates adopted across multiple delivery workflows.
30% faster build and deployment cycles. Standardized delivery across teams.
Approach
01
I've seen architectures that were technically correct and completely useless. The first question is always what the business actually needs — regulatory constraints, cost position, growth timeline. The architecture follows from that.
02
Most architecture recommendations arrive as 'this is best practice.' That's not a decision — it's a deflection. I frame every choice in terms of what it costs, what it protects, and why it fits this situation specifically.
03
A recommendation handed off and never seen again isn't architecture — it's a document. I stay through implementation because that's where the real decisions happen and where the design either holds or doesn't.
Technical Insights
Cloud migration is sold as a universal upgrade. It rarely is.
Los sistemas financieros regulados imponen restricciones que las arquitecturas event-driven comúnmente ignoran. Aquí está lo que aprendí implementándolas.
"Zero-downtime migration" is on every architecture slide deck. The implementation is almost never described honestly.
Services
Translating business requirements into scalable Azure solutions. From assessment to implementation roadmap, with decision clarity at every stage.
End-to-end planning for legacy and multi-cloud environments — governance, cost position, zero-downtime execution.
Supporting engineering teams with architecture decisions, delivery frameworks, and alignment from strategy to ship.
Contact
Open to consulting engagements, architecture advisory, and technical leadership roles.