Why start again?
I started a personal blog to document technical projects, but I didn’t build a consistent habit around it. Over time, I realised that a useful notebook should be more than a collection of code snippets or project summaries. It should also show how my thinking develops.
I’m restarting this blog as a place to record what I learn, explain ideas in my own words, and look back at the decisions and habits that shape my progress.
Beyond code
Software engineering is still at the centre of my professional life, especially backend systems and the infrastructure that makes products reliable. At the same time, I’m curious about how AI changes the way we build software, how financial systems work, how economic forces influence everyday decisions, and what psychology and philosophy can teach us about thinking clearly.
These subjects may look unrelated at first. For me, they share one theme: understanding how systems work, whether the system is a software platform, a market, or my own routine.
A goal that needs a process
One of my career goals is to build the skills and evidence needed to pursue software engineering opportunities in Singapore. A goal by itself does not make progress happen. I need a repeatable process: study deliberately, build things, communicate clearly, seek feedback, apply consistently, and review what the results are teaching me.
This blog will help me make that process visible to myself. It can also become a record of projects and lessons that I can share when they are useful to other people.
Learning in public
I don’t want every post to sound like a polished success story. Some posts will explain a technical concept; others will be reading notes, experiments, career retrospectives, or questions I am still working through.
When I write about a topic, I want to separate what I know from what I suspect, include sources when appropriate, and state what I would do differently next time.
The standard I want to keep
My aim is not to publish every day or to make this site look busy. It is to keep showing up, write down useful lessons, and turn reflection into a concrete next step.
This is the beginning of that practice. The next chapter will be shaped less by what I say I want to do and more by the work I can point to.