About me

Architect and domain shaper. I design systems and model business domains to create solutions that fully reflect your business logic.

Who I am

My name is Héctor Barrientos Margolles. I'm an engineer and software designer with over 15 years of experience shaping digital ecosystems that scale with business alignment.

My background combines deep technical expertise with a strategic mindset — bridging business goals and engineering execution.

Architecture goes beyond structure: it's about aligning technology with business logic and clear domain boundaries.

Work Philosophy

Logic, structure, clarity

I build systems and teams around clarity and intent.

Hexagonal architecture is my foundation for maintainable, testable systems — guided by domain understanding rather than frameworks.

Domain-Driven Design helps me capture business complexity through contextual language and collaboration, turning ambiguity into shared understanding.

Clarity over complexity is my constant principle — in code, communication, and design.

Design Principles

Simplicity: Software should be transparent, not a black box.

Scalability: Systems must evolve naturally with business growth.

Maintainability: Code should be readable, enjoyable, and meaningful.

API First: I conceive every component as an API—with clear intention, semantics, and contracts between different parts of a system.

Human alignment: Architecture exists to serve people and business needs, not the other way around.

Tech Stack and Principles

I craft systems where performance, clarity, and extensibility come first. Technology boundaries are volatile—don't marry yourself to the same stack. The business problem determines the technology, not the technology the problem.

Backend & APIs

  • • Node.js & TypeScript for expressive, event-driven services.
  • • PHP (Slim, Laravel) for stable, business-centric backends.
  • • Adobe Commerce (Magento 2) for modular e-commerce architectures.
  • • REST & GraphQL for integration and domain exposure.
  • • Microservices when they serve autonomy — not fashion.

Architecture & Patterns

  • • Domain-Driven Design as a way to align code with business language.
  • • Hexagonal & Clean Architecture for maintainability and testability.
  • • CQRS & Event Sourcing when clarity and traceability matter.
  • • SOLID & simplicity as practical ethics, not dogma.

Infrastructure & Delivery

  • • Docker for isolated, reproducible environments.
  • • CI/CD pipelines to automate what should never depend on luck.
  • • Monitoring & observability to keep systems honest.
  • • Databases designed for meaning, not just storage.
  • aboutPage.techStack.infraDevOps.item5

My vision

AI has fundamentally changed how we relate to the business world. Technology, through AI, is pushing engineers toward the business layer, blurring the boundaries that once existed between engineers and domain experts.

Engineers are now more designers and business strategists than ever. Technical details belong to the entity implementing business processes—the AI. The engineer's role is to supervise, design systems, and correct the machine.

This shift means engineers must focus on domain design and business logic, not implementation details. The business determines the technology, and AI handles the execution.

Shall We Work Together?

If you share this vision of software as art and living system, let's talk.

Start conversation