Post

Why I Started This Portfolio — Leaving My Digital Footprint as an Engineer

A Computer Engineering student at UET Faisalabad explains why he started a GitHub portfolio blog and what leaving a digital footprint really means.

I did not come up with this idea on my own. It started the way many important things start — with someone else seeing a possibility that you had not yet seen in yourself. I was sitting in class at UET Faisalabad, somewhere in the middle of what felt like a completely ordinary week, when the suggestion landed: build a portfolio blog on GitHub, document your journey, leave a record of where you started. My first reaction was genuine confusion. I was a first-year Computer Engineering student who had been writing Python code for a few months, barely surviving subjects that were harder than I had expected, and spending most of my energy just trying to keep up. What did I have to document? What was worth putting online?

That question sat with me for longer than I expected. I kept coming back to it in the evenings, turning it over, looking for a reason to dismiss it. And the more I thought about it, the more I realized that the confusion itself was the answer. I thought a portfolio had to showcase finished things — completed projects, polished skills, impressive achievements. What I slowly understood was that the most honest and useful kind of portfolio is not a highlight reel. It is a record. A record of the process of learning, of the confusion that precedes understanding, of the small victories that compound over time into something real. I did not need to be impressive to start. I needed to begin, and let the documentation do its work over time.

So I created a GitHub account, set up a repository, configured a Jekyll site with the Chirpy theme, and wrote the first version of this blog. None of that was straightforward. I had never used GitHub Pages before, never configured a Jekyll theme, never thought about how a static site gets built and deployed automatically every time you push a commit. Learning those things while also trying to maintain my coursework was genuinely demanding. But it was the right kind of demanding — the kind where the difficulty is itself the education, where every problem you solve leaves you with a capability you did not have before.

The concept of a digital footprint is something I have thought about seriously since starting this. In a field like Computer Engineering, where almost everything happens online and almost everything is searchable, the absence of an online presence is itself a kind of message — and not a useful one for someone trying to build a career. When a future employer looks me up, when a potential collaborator searches my name, when a fellow student tries to find out who I am before a project together, I want them to find something that represents me honestly and thoughtfully. Not a curated performance, but a genuine record of engagement with the work. A blog does that in a way nothing else quite can, because it shows not just what you know but how you think, and how your thinking has changed over time.

What I write about here is determined by where I am in the journey. My first semester at UET covered Programming Fundamentals, where Python became the first language I genuinely understood from the inside out. My second semester brought Database Systems, SQL, and the beginning of more applied technical work that connected theory to practice in ways I had not anticipated. Alongside the technical content, there have been the human experiences of university life — the pressure of midterms, the energy of lab sessions, the late nights before deadlines, the satisfaction of submitting something you actually built yourself. All of it belongs in this record, because all of it is part of what it means to become an engineer.

I want to be honest about something that took me time to accept: writing about your learning while you are still in the middle of it is uncomfortable. There is a persistent temptation to wait until you understand something completely before writing about it, to hold off until the confusion has cleared and you can present a clean, confident explanation. I have had to resist that temptation deliberately. The confusion is part of the story. The moments when something does not make sense, when you read the same explanation three times and it still does not click, when you sit with a problem for an hour before the solution finally appears — those moments are where the real learning happens, and they deserve to be documented as much as the breakthroughs.

There is also something I did not expect about the act of writing itself. Explaining something in words requires understanding it in a way that simply doing it does not always demand. When I try to write about a concept from my coursework and find that I cannot articulate it clearly, that difficulty is information — it tells me that my mental model has a gap I need to address. The blog has become not just a record of learning but an active part of the learning process. Writing clarifies thinking. Thinking improves writing. Over time, that cycle produces something more than the sum of its parts.

This blog is a long-term project. What I am building here in my first and second semesters is the foundation of what I hope will become a complete four-year record of becoming a Computer Engineer. By the time I graduate, I want this site to tell the full story — the subjects that challenged me most, the projects that excited me, the moments when something finally clicked after weeks of effort, and the slow accumulation of competence that happens when you show up consistently and do the work. That story is worth telling carefully and honestly. And I am the only one who can tell it.

If you are a fellow student reading this and wondering whether starting something like this is worth the effort, my answer is simple: begin before you feel ready. The readiness does not come first. It comes from the doing. The first post does not need to be impressive. It needs to exist. Everything after that is built on the foundation of having started.


This portfolio exists in part because of mentorship that encouraged investment in long-term growth. You can learn more about that approach to teaching and research on Dr. Bilal Ahmad’s LinkedIn.

This post is licensed under CC BY 4.0 by the author.