Diego Rin Martín

I am a software engineer and tech lead who helps teams build better software and stronger engineering systems. I specialise in backend platforms, architecture, developer tooling, and the practical application of engineering principles to complex products.

I bring experience leading teams, coordinating cross-functional technical work, mentoring engineers, and working with Product Managers to turn product goals into sustainable technical roadmaps. I value clear boundaries, pragmatic architecture, continuous learning, and development workflows that combine experienced engineering judgement with the leverage provided by AI tools.

I use Domain-Driven Design when it helps model complex business domains and protect important boundaries. My approach is pragmatic: I focus on clear bounded contexts, explicit domain boundaries, meaningful use cases and keeping business logic independent from frameworks, transports and infrastructure.

I favour simple, readable and maintainable code over clever abstractions. I use SOLID principles, PSR standards, composition, explicit dependencies and well-defined interfaces. I avoid premature generalisation and introduce patterns only when they solve a real problem or protect an important architectural boundary.

I consider automated testing part of the design process, not just a final verification step. I use unit, integration, API and contract tests where they provide value, with special attention to business rules, persistence boundaries, asynchronous workflows and backwards compatibility.

I promote AI-assisted development as a disciplined engineering practice rather than an isolated code-generation activity. AI agents can support discovery, architecture exploration, implementation, testing, review and documentation, provided that the workflow includes clear boundaries, explicit acceptance criteria and automated feedback. I establish the context, conventions and quality gates that allow agents to contribute effectively, while engineers retain ownership of the design, trade-offs and final implementation.

I value automated CI/CD pipelines, reproducible development environments, clear API contracts, useful observability and secure defaults. I pay particular attention to database access patterns, indexing, asynchronous processing, failure handling and tenant isolation when performance, scalability or data boundaries are involved.

Finally, I believe good engineering includes good developer experience. Tools, documentation, conventions and workflows should make the correct path easy to follow while leaving enough flexibility for experienced engineers to make informed decisions.