Javiera Laso
Lead Engineer Consultant · THOUGHTWORKS
I’m a Lead software engineer and architect with a background in biotechnology. I specialize in modernizing legacy systems, transforming them into scalable, efficient, and maintainable solutions. I focus on applying Domain-Driven Design (DDD) principles to create software that not only meets technical requirements but also aligns with business goals.
I have experience designing modular, cloud-ready architectures and using techniques like microservices and event-driven design to solve complex challenges. I’m passionate about continuous learning and improvement, and I enjoy mentoring teams and promoting best practices in software development. My approach combines deep technical knowledge with a practical understanding of business objectives, ensuring that the solutions I deliver are both effective and future-ready.
PRESENTATIONS
The Cost of Good Intentions: Anti-Patterns in Architecture Modernization
Modernizing legacy systems seemed exciting…until I found myself absorbed in rewrites, facing business blockers, and watching tech debt pile up instead of shrink. In this talk, I’ll share the biggest traps I’ve seen and experienced firsthand while working on modernization efforts in large organizations—and what helped us avoid (or recover from) them. From picking the wrong architecture patterns too early to losing stakeholder trust halfway through, I’ll walk through real examples of what not to do, along with the principles and strategies that helped us get back on track. Whether you’re breaking down a monolith or updating a business-critical system, I’ll help you steer clear of common pitfalls and make smarter, more sustainable decisions.
What This Talk Will Answer:
-What are the most common and costly mistakes teams make during architecture modernization?
-How do you choose between refactoring, rewriting, or rearchitecting a legacy system?
-How can Domain-Driven Design reduce risk and improve focus in modernization efforts?
-What strategies keep modernization aligned with business priorities and avoid loss of momentum?
-How do you avoid turning tech upgrades into long-running, low-impact projects?