A notebook in progress

Notes from the build.

Small lessons, project reflections, and honest observations from learning how thoughtful software gets made, understood, and improved with data.

What test automation teaches me about good software

Writing end-to-end tests for a student management system changed how I look at a feature. A login screen is not only a form: it is a promise that the right person can enter, that a wrong credential is handled clearly, and that the next step behaves predictably.

With Playwright and Selenium, I practice checking the happy path as well as the edges: invalid input, authentication failures, CRUD flows, and behavior across browsers. Postman adds another useful perspective by making API responses visible before they become a confusing front-end issue.

The most valuable part is the record left behind. A clear reproduction step, expected result, and actual result turns a vague bug into a shared problem the team can solve.

Learning by moving between code and people

My BSc.CSIT journey has given me the fundamentals, but projects give those fundamentals a place to breathe. I learn fastest when I can build a small web experience, inspect what is not working, and ask better questions the next time around.

Being part of the organizing team at the MBM IDEAX Hackathon taught me a parallel lesson: technical work is also coordination, communication, and making room for other people to do their best work.

Why I keep making small tools

My projects range from a Pomodoro calendar and task manager to YouTube data analysis and NeuroNav. They are different on the surface, but each begins with a practical question: how could this become easier to understand, plan, or use?

Small tools make experimentation feel approachable. They let me practice structure, interface decisions, data handling, and debugging without losing sight of the person using the result.

Finding meaning in the numbers

I am increasingly drawn to data because it helps turn a broad question into something we can explore carefully. In my YouTube Data Analysis project, I used Python, Pandas, and Matplotlib to clean a dataset, look for patterns, and present trends in a way that could be understood beyond the raw numbers.

Completing the Data Analyst Associate track on DataCamp strengthened that interest and gave me a more structured way to practice analysis. It helped me connect programming with investigation: asking a useful question, preparing reliable data, choosing an appropriate view, and explaining what the result actually tells us.

I am still growing in this area, but data analysis is becoming an important part of how I approach projects. I want to keep learning how thoughtful analysis can support better products, clearer decisions, and more useful experiences.