About Me
About Me
I am Muhammad Anas, a Computer Engineering student at UET Faisalabad, and this portfolio is where I am documenting how this field has actually felt to learn, one semester at a time, rather than just listing the skills I have picked up along the way. I started university with a fairly vague idea of what Computer Engineering would involve something about computers, something about building things and it has taken an entire semester of actual coursework to turn that vague idea into something I can describe with any real confidence.
My interest in technology did not begin in a classroom. Like a lot of people my age, it started with curiosity about how the apps and devices I used every day actually worked underneath the surface. That curiosity stayed mostly passive for a long time, since wondering how something works is very different from sitting down and learning to build it yourself. University, and this semester in particular, is where that shift from passive curiosity to active skill-building finally started happening, sometimes uncomfortably, but consistently.
This semester, my main academic focus has been Programming Fundamentals and Database Systems, two courses that, on paper, sound like fairly standard introductory subjects, but that turned out to shape almost everything else I did afterward. Programming Fundamentals introduced me to Python, starting from the most basic syntax and gradually building up to programs with real, layered logic conditions inside conditions, loops that depend on earlier calculations, functions that organize what would otherwise be repetitive code. Database Systems, taught alongside it, introduced an entirely different way of thinking, centered on structure, relationships, and the discipline required to keep data trustworthy rather than just present. Both courses were taught by Dr. Bilal Ahmad, and the way he connected programming logic and data structure back to real, large-scale problems often pointing toward the kind of high-quality datasets used in serious machine learning work gave both subjects a bigger context than I expected from a first semester introduction.
Beyond these two core courses, I also picked up a working understanding of Digital Logic Design, which pulled my attention toward the hardware side of computing for the first time, and a beginner’s introduction to Machine Learning, which felt like a glimpse of where a lot of this programming and data knowledge eventually leads. I am not claiming expertise in any of these areas yet I am still very early in this journey, closer to the beginning than the middle of it. What I can say honestly is that I now understand, at a basic but real level, how software is written, how data is structured and queried, how digital circuits make decisions, and how a simple machine learning model can be trained on real data to make predictions.
Technically, my current toolkit includes Python and C#, a working knowledge of MySQL for designing and querying databases, basic circuit simulation using Microwind, and early experience with Python’s data and machine learning libraries such as pandas, matplotlib, seaborn, and scikit-learn. None of these are skills I would call mastered; they are skills I am actively building, semester by semester, project by project, and I expect this list to look noticeably different a year from now.
What I enjoy most about this field, more than any specific language or tool, is the particular kind of problem-solving it demands — breaking a vague, sometimes confusing requirement down into small, precise, logical steps, whether that requirement is a discount calculator, a database schema, a logic circuit, or a prediction model. That habit of thinking, more than any single technical skill, is what I am trying to build deliberately this semester and every semester after it.
This portfolio exists to keep an honest record of that process. The posts here are not polished case studies written after the fact to look impressive; they are closer to a first hand account of what learning Computer Engineering has actually looked like for me the confusion at the start of each new topic, the slow grind of practice, and eventually, with enough repetition, the moments where something genuinely clicks. I am sharing it publicly because I would rather document this journey honestly as it happens than try to reconstruct a tidy version of it later, once the details and the difficulty have already faded from memory.
Outside of coursework, I try to spend time exploring small side projects connected to whatever I am currently learning, even when they are not required for any assignment. Some of these experiments work out and end up shaping how I approach the next official project; others quietly fail and get abandoned after teaching me exactly why a particular approach does not work. I have started treating both outcomes as equally useful, since the ones that fail usually teach me more specifically what to avoid than the ones that succeed teach me what to repeat.
If there is one thing I want this portfolio to communicate beyond the list of courses and tools, it is that I am still early in this process and comfortable saying so directly. I am not presenting myself as someone who already has this field figured out; I am presenting an honest snapshot of a student a few months into a much longer path, with enough curiosity to keep going and enough humility to know how much further there is left to learn.
I also think a lot about why I am bothering to keep this kind of public record at all, rather than just letting each course end quietly with a grade and moving on. Part of the answer is practical a documented journey is something I can point to later, whether that is for an internship application, a graduate program, or simply my own future self trying to remember how a concept first made sense. But a bigger part of the answer is that writing about a topic forces a kind of clarity that just finishing an assignment does not. Explaining a discount calculator, a database schema, or a logic circuit in plain language, in a way meant for someone else to follow, has repeatedly exposed gaps in my own understanding that a working program or a passing grade would have quietly let me ignore.
I expect this About page itself to be revised more than once as the picture changes new courses, new tools, new mistakes worth being honest about. For now, this is an accurate description of where I am: a first semester Computer Engineering student at UET Faisalabad, building the basic vocabulary of programming, data, and circuits one course at a time, and trying to write about that process as truthfully as I can while it is still happening, rather than after the fact.