I started with code.Security changed howI saw systems.

My first professional years were spent building web applications — PHP, React, servers, deployments, the ordinary work of getting software into people’s hands. That period taught me how systems are actually assembled, which turned out to matter more than any single technology I learned along the way.

Security came next, and it rearranged my thinking. Auditing a blockchain platform, assessing fintech APIs, testing mobile applications and reviewing code for a living forces you to read a system the way it will be read by someone trying to break it. You stop seeing features and start seeing boundaries, trust assumptions and the places where two components disagree about who is responsible for what.

Infrastructure widened the frame again. Managing networks, firewalls, servers and cloud environments meant the consequences of a design decision were no longer confined to a repository — they showed up in availability, in cost, in how quickly a team could ship. DevSecOps was the natural synthesis: security as part of delivery rather than a gate placed in front of it.

Leading an IT department, and now technology as a whole, changed the unit of work. Architecture decisions became budget decisions. Engineering velocity became a business number. Security governance became a conversation with people who do not read code. The technical judgement still applies — it just has to be translated.

Artificial intelligence is the current layer. With Andrea, our in-house real-estate intelligence initiative, the interesting problem was never the model. It was the integration: connecting real-estate knowledge, business data, CRM workflows and customer interaction so that the AI does something useful inside the operation rather than beside it.

What I care about, across all of it, is that the technology holds up. That it stays available, stays defensible, and stays understandable to the people who have to run it after the meeting ends.