Chapter 02About

I build software that survives the day after launch.

For most products, launch day is the easy part. The real work starts the morning after, when real users break things in ways no one planned for. That's the phase I care about most.

By Rusty Lopez

Full Stack Engineer · Abu Dhabi, UAE

5 min read

The short version

I'm a Filipino full stack engineer based in Abu Dhabi. Most of my work lives inside the systems people don't see, CRM platforms, ERPs, internal tools, and the APIs that hold all of it together. The kind of software that runs the business, not the marketing site.

I started by teaching myself PHP late at night, and somewhere along the way it turned into shipping enterprise software for teams across the UAE. Real estate, cloud infrastructure, AI assisted lead scoring. The work changes, but the shape of it usually doesn't.

The best software doesn't feel like software. It just feels like getting things done.

Something I keep telling myself

Today, I work with founders, ops teams, and engineers to take messy real world problems and turn them into systems that quietly keep working, long after the launch announcement has scrolled off the timeline.

at work on an anonymous system, 2026.

fig. 01

How I work

Four ideas I keep coming back to.

Every project is different, but how I approach them isn't. These are the convictions I keep falling back on.

01
Boring tech, where it counts.
I'd rather use a battle-tested stack and ship in two weeks than chase the trend and debug for two months. Predictable beats clever, every time.
02
Read the system before changing it.
Most production bugs are misunderstandings, not bad code. I spend more time reading existing systems than writing new ones, and it usually pays off.
03
Optimise for the day after launch.
If a feature can't be fixed at 11pm by someone who didn't build it, it's not really shipped. Logging, monitoring, rollback paths: non negotiable.
04
Write less, decide more.
The hardest part of software isn't the code: it's deciding what shouldn't exist. The smallest reasonable solution beats the "complete" one.

What I work with

A small set of tools, used deliberately.

I don't pick stacks. I pick tools that have already proven they survive in production, and use them for things they're actually good at.

Frontend: I build production interfaces in Angular and Next.js: accessible, fast, and shaped around the workflows people actually use, not the ones product specs imagine.
Angular
Next.js
TypeScript
React
Tailwind
Backend: Most of my server work is Laravel and Lumen: clean APIs, queue workers, ERP grade business logic, and the validation everyone forgets to write.
Laravel
Lumen
PHP
Node.js
REST
JWT
Data: MySQL and PostgreSQL for transactions, Redis for everything that needs to be fast. I care more about query plans and indexes than ORM cleverness.
MySQL
PostgreSQL
Redis
Pinecone
Infrastructure: AWS for compute and delivery, with the kind of monitoring, failover, and rollback paths you only appreciate at 2am.
AWS
EC2
S3
RDS
CloudFront
Nginx

The long way here

From late-night tutorials to production systems.

2016
The Beginning
Started learning to code during senior high school. At the time, I was curious about how websites worked behind the scenes and began exploring different parts of the internet, including how systems operate, how data flows, and how security works. This curiosity led me to experiment, learn, and understand the fundamentals of programming and web development. It wasn’t structured at first, but it built the foundation for everything I do today.
2018
Choosing IT
Pursued a Bachelor of Science in Information Technology at the University of the East, one of the well-known schools for IT in the Philippines. At the time, I was also heavily into gaming, which naturally drew me toward technology and how systems worked behind the scenes. While my parents initially wanted me to take a different path, I chose to pursue IT because it was something I genuinely enjoyed and wanted to build a future in. This decision marked the point where curiosity turned into commitment, and where I became more serious about software development, problem-solving, and turning interest into real skills.
2020
Learning by Building
During the pandemic, learning shifted online, but being in a technical field meant more hands-on work and projects. This period pushed me to apply what I was learning in more practical ways, from building simple systems to understanding how real-world applications function. I also started taking on small freelance projects, building websites and working with different requirements. This was where I began experiencing real client work, deadlines, and the responsibility of delivering functional solutions.
2022
Stepping Into Real Systems (OJT)
Completed my internship as a Web Developer at the University of the East, where I worked on real systems used by organizations across the Philippines. I contributed to building and improving features, focusing on both frontend and backend. I collaborated with teams on UI improvements, performance optimization, and deployment processes, gaining exposure to how real systems are developed, tested, and released. This experience introduced me to real-world workflows, deadlines, and the importance of writing reliable and maintainable code.
2023
Transition to Professional Engineering
Graduated with a degree in BSIT, majoring in Software Development and Programming, and transitioned into a full-time Software Engineer role at a fintech company focused on identity solutions and card systems in the Philippines. Working alongside experienced developers, cybersecurity specialists, and cross-functional teams, I was exposed to real production environments where stability, security, and performance were critical. I contributed to building enterprise applications, developing REST APIs, integrating third-party services, and resolving production issues. This phase significantly strengthened my technical foundation, communication, and ability to work under pressure in a professional engineering environment.
2024
Building Systems That Matter
Moved into a Full Stack Engineer role at Crompton Partners Estate Agents in Abu Dhabi, working on internal CRM systems that support real estate operations. I handle both backend and frontend development, building and maintaining features across modules such as leads, listings, and internal workflows. My work involves integrating third-party platforms, improving system performance, and resolving production issues that impact daily business operations. This role further developed my ability to build scalable systems, manage complex workflows, and deliver solutions that directly support real users and business teams.
NOW
Focused on Impact and Scale
Currently focused on developing and maintaining CRM systems, internal tools, and integrations used in real-world business environments. My work involves optimizing performance, improving data flow, automating processes, and ensuring systems remain stable and reliable under daily operational use. The goal is to build solutions that are practical, scalable, and aligned with how teams actually work.

Currently focused on developing and maintaining CRM systems, internal tools, and integrations used in real-world business environments. My work involves optimizing performance, improving data flow, automating processes, and ensuring systems remain stable and reliable under daily operational use. The goal is to build solutions that are practical, scalable, and aligned with how teams actually work.

End of article

That's most of it. If any of it sounded right for what you're building, let's talk.

Start a conversation See what I've built

Rusty

Abu Dhabi · 2026

Fin.

I build software that survives the day after launch.

Four ideas I keep coming back to.

Boring tech, where it counts.

Read the system before changing it.

Optimise for the day after launch.

Write less, decide more.

A small set of tools, used deliberately.

From late-night tutorials to production systems.

The Beginning

Choosing IT

Learning by Building

Stepping Into Real Systems (OJT)

Transition to Professional Engineering

Building Systems That Matter

Focused on Impact and Scale

2016The Beginning

2018Choosing IT

2020Learning by Building

2022Stepping Into Real Systems (OJT)

2023Transition to Professional Engineering

2024Building Systems That Matter

NOW Focused on Impact and Scale

That's most of it. If any of it sounded right for what you're building, let's talk.