I have been working with software development for a few years, and over time I have gained a clearer understanding of what keeps me interested in this field: building products that solve real problems, supported by code that holds up over time and makes sense to the team that comes next.
I work across the full web development stack. On the frontend, I use React, Next.js, and TypeScript. On the backend, I work with Node.js, Java with Spring Boot, and PHP with Laravel, as well as databases such as PostgreSQL and Oracle. Having this end-to-end perspective matters in practice because technical decisions rarely stay within a single layer.
Throughout my career, I have worked in very different contexts, including critical corporate healthcare systems, customer service platforms, and legacy modernization projects. Each one taught me things that are difficult to learn any other way. I learned how to approach an unfamiliar codebase without judgment, understand why previous decisions were made, and propose improvements without disrupting what is already working.
I also learned that technical quality is often one of the first things to be compromised when deadlines become tight, precisely when it matters the most. I work with Clean Code, SOLID, Design Patterns, and automated testing not simply because they are considered good practices, but because I have seen what happens when a team decides it will “refactor later.”
When I am not working with code, APIs, or databases, I am probably reading something or being supervised by a cat. Feel free to reach out to talk about software development, architecture, legacy modernization, or books.



