// 01
Architecture
Designing boundaries, managing complexity and making trade-offs in real production systems.
Tiago Perrelli / Senior Software Engineer
// systems
I build software that evolves with the business.
Senior Software Engineer focused on software architecture, full-stack systems and the evolution of production software.
15+ years building software across products, APIs, existing systems and SaaS — evolving from PHP and Laravel through JavaScript, Vue.js and more recent work with Node.js, Python, TypeScript and Next.js.
01 / Engineering
Software has a history.
// decisions under constraints
Most production systems weren't designed all at once. They evolved through deadlines, business decisions, changing requirements, new technologies and engineers who came before us.
My own work has followed that path: from PHP and existing systems to Laravel, JavaScript, Vue.js, full-stack applications and more recent work with Node.js, Python, TypeScript and Next.js.
Architecture, to me, is about understanding where a system is today, knowing where it needs to go, and choosing the right way to get there.
02 / Practice
Architecture, engineering and the career context around both.
The technology matters, but it is evidence. The deeper work is deciding how systems should evolve under real constraints.
// 02
Engineering
Building and evolving full-stack systems across APIs, backend services, frontend applications, performance, testing and production environments.
// 03
Career
Lessons from years working remotely with international teams and building a career beyond the local market.
03 / Writing
Notes on decisions, trade-offs and production systems.
Writing is treated as proof of thinking: the place for deeper technical judgment, not generic tutorials.
Architecture
When the Strategy Pattern makes things worse
A note on how good abstractions still fail when they hide the wrong kind of change.
Reading time TBD · Date TBD
→
Engineering
I didn't need a microservice. I needed a boundary.
What production systems teach about separating responsibilities before separating deployment units.
Reading time TBD · Date TBD
→
Career
What international teams changed about the way I write software
Communication, review quality and decisions that survive distance, time zones and context gaps.
Reading time TBD · Date TBD
→
04 / Building
Products and tools as evidence of engineering in motion.
The goal is not to turn the personal site into a product landing page. These projects show how engineering, product and constraints meet.
Avaly↗
A personal SaaS in progress focused on authentic, auditable reviews.
Product / SaaS / Operations
Building products is where engineering meets product, distribution and business constraints.
phx↗
A CLI that helps PHP monorepos run only the tests affected by a change.
PHP / CLI / Testing / Monorepos
A technical product shaped by test feedback loops, monorepo boundaries and practical developer experience.
05 / Experience
15+ years building software.
Experience across different generations of web software: PHP and Laravel, JavaScript and Vue.js, APIs, SaaS, production systems, legacy modernization and newer full-stack work with Node.js, Python, TypeScript and Next.js.
15+
Years building software
Backend: PHP / Laravel, Node.js, Python, APIsFrontend: JavaScript, TypeScript, Vue.js, Next.jsSystems: SaaS, Distributed Systems, Legacy Modernization
International remote experience
Years working with international clients and distributed teams across different stages of product maturity.
LET'S TALK
Let's talk about software.
Building something interesting, working on a challenging system, or looking for an experienced engineer?