I've always enjoyed figuring out how things work.

My interest in programming began in 2012 when I picked up a programming book from my local library.

I didn't know much about programming or what I could actually accomplish with it. I was simply curious about how it worked.

That first book led me to others. I started learning about C, C++, PHP, Symfony, and different approaches to building software. I spent a lot of time reading, experimenting, getting things wrong, and trying to understand why things worked the way they did.

I didn't have a roadmap or anyone guiding me through the process. I learned because I enjoyed the challenge.

The more I understood, the more possibilities I started seeing.

Around 2013, I began exploring an idea based on something I knew firsthand: the challenges homeowners face finding reliable service professionals and the difficulties small contractors face running their businesses.

The original concept was a platform connecting homeowners with local professionals.

Over time, I explored different approaches. One became contractor-management software for customers, estimates, invoices, jobs, and other day-to-day business operations.

That same idea eventually evolved into HomeProSG.

Today, I'm developing HomeProSG around a local network of service professionals who can work together, share the cost of operating the platform, and refer customers through a dedicated local service network.

The idea has changed quite a bit over the years. So have the technologies I've used to approach it.

But the underlying goal has always been to find a practical way to solve a real business problem.

I like change. I like challenges. And I enjoy learning something new.

That's probably one of the biggest reasons software development has held my interest for so long.

There are so many different technologies, problems, and ways to approach building something that I don't see myself running out of things to explore.

It's also why I build automation tools.

Doing the same repetitive tasks every day doesn't hold my interest. If I find myself repeating a process, I start thinking about how I could automate it or improve the way it works.

That thinking eventually led me to develop my own project workflow, browser automation, and engineering review systems.

As my projects became more complex, I needed better ways to organize the work, coordinate development, manage requirements, and verify the results.

So I started building those tools too.

I started learning programming long before AI coding assistants were available.

That foundation helped me understand programming concepts, application structure, and how different technologies work together.

Today, I use AI-assisted development as part of my workflow. I establish the requirements, make architectural and product decisions, coordinate implementation, review the results, and determine whether the work meets its intended purpose.

I believe that understanding the problem and knowing what you're trying to build are just as important as writing the code.

My projects now span mobile applications, full-stack platforms, cloud infrastructure, data systems, browser automation, and development tooling.

Each has given me something new to learn and another set of problems to work through.

For more than a decade, software development was something I pursued because I genuinely enjoyed doing it.

Now, with several of my own software products getting closer to release, I'm making the transition to software development as my full-time profession.

I'll continue building my own products, but I also want to use what I've learned to help other people bring their ideas to life.

Having operated my own business for years, I understand that software isn't just about technology. It needs to serve a purpose, solve a problem, and make sense for the people using it.

That's the approach I bring to ProjectFlowPro.

I started programming because I wanted to figure out how it worked. Thirteen years later, I'm still learning, still building, and still finding new challenges to take on.