I finally got my personal website up and running. It is hosted on Firebase, sitting somewhere on the internet and looking far more organized than I am. Originally, I thought it would just be a simple portfolio page with my name, a few projects, some contact information, and that would be enough. But after spending time building it, I realized I wanted it to be more than a digital business card.
More than a portfolio
I wanted a place where I could keep track of what I am learning, what I am building, and occasionally what I am thinking about.
Right now, I am in a pretty interesting phase of life. I recently graduated from university and started working as a Business Analyst. The funny thing is that my day-to-day work is not just business analysis. A lot of it involves UI/UX prototyping in Figma, discussing requirements with stakeholders, thinking about user flows, and trying to make sure developers can actually build whatever ends up being designed.
Somewhere along the way, I realized that software is not really about screens or code. It is mostly about people trying to understand each other. Users want something. Businesses want something. Developers need something. And somehow all of those things have to meet in the middle.
That is probably the part of the job I enjoy the most.
Coming from a Software Engineering background, I naturally look beyond the visual layer of a product. When I see a screen, I start thinking about data flow, permissions, edge cases, error handling, and all the little details that nobody notices when things work correctly. At the same time, working in analysis and design has taught me that technical correctness alone does not automatically create a good experience.
A feature can be perfectly implemented and still confuse people.
That is something university never really teaches you.
What work is teaching me
One thing I have been learning recently is that clarity is surprisingly valuable. A lot of work is not about inventing something brilliant. Sometimes it is just about asking better questions, identifying assumptions, and turning vague ideas into something concrete enough for a team to discuss. A rough Figma prototype can often solve more misunderstandings than a long meeting ever could.
This website is a small example of that mindset. It is not a huge project, but it is mine. I can experiment with ideas, write about things I am learning, document mistakes, and maybe share a few useful insights along the way. It also gives me an excuse to stop letting random thoughts disappear into forgotten notes and chat logs.
Why I want to write things down
As for what you will find here, it will probably be a mix of work experiences, UI/UX observations, business analysis lessons, personal projects, and whatever else happens to catch my attention. Some posts will be technical. Some will not. Some will probably start with a serious topic and somehow end with me talking about football, music, or a random problem I ran into at work.
I do not really have a grand plan for this blog. I am not trying to position myself as an expert, and I am definitely not trying to become a productivity guru. I am still figuring things out, just like everyone else. But I think there is value in documenting the process while it is happening.
Maybe a few years from now I will look back at this post and laugh at how little I knew. Honestly, that would probably be a good sign.
For now, this is simply a place to learn in public, keep track of my journey, and leave a few breadcrumbs for my future self.
Let us see where it goes.