A Journey into Engineering

Chamaco - To this day, I still feel like my younger self, fascinated by computers, eager to repair them, and enthusiastic about creating webpages.

Early Experiments in Hardware

My journey into the world of software engineering started with my very first PC. It was a Windows machine running either Windows 95 or 98. I was too young to care about the specs back then, but little did I know that this humble computer would set the stage for my future

At the time, we had only a few floppy disks with games, so my attention soon turned to the machine itself. Like a mad scientist, I took it apart to unravel its mysteries. Through trial and error, I learned about RAM, Motherboards, and an enigmatic BIOS screen.

Ultimately, that BIOS screen left me locked out of my first computer. I could piece a computer back together but not remember a BIOS password after losing the sticky note where I had jotted it down. Despite this, my curiosity for technology was ignited, and I was determined to explore further.

Venturing into Software

My second computer, a humble prebuilt from Walmart, soon followed. Similar to the first, it was a short time before I had this one on the operating table. Except this time, I was piecing it back together with hand-me-down parts from a family member who had moved back to the States. He was an older cousin with far more technical experience. Had he been here to show me how to reset the BIOS password, I probably would have had my first computer for longer.

The parts he gave me unlocked a whole new world of powerful software like the Adobe Creative Suite. With this newfound arsenal, I delved into graphic design, experimenting with Photoshop and a Wacom tablet. I transitioned from traditional drawing to more abstract forms of expression. This creative outlet allowed me to make significant contributions to my school yearbook class, key art contests, and local businesses.

Simultaneously, I maintained a keen interest in hardware and software. To fuel my hobbies, I worked part-time for local businesses and took on side jobs from family and friends, such as repairing their phones and computers. Through all of this, my name spread, and people started asking for more complicated tasks like jailbreaking/rooting mobile phones or phishing MySpace credentials for pranks between friends. I eventually had to turn jobs down that seemed too "black hat." Unfortunately, this tarnished my view of my software skills at the time since it felt like an easy way to get into trouble.

As high school graduation approached, I had scholarships for graphic design but an even stronger urge to opt for engineering. Social influences played their part, but a career built around tinkering seemed the truest to me, so I stepped away from said scholarships and design work. Additionally, because of the negative connotation I had associated with my software skills, I ended up opting for a degree in Electrical Engineering.

Building and Learning

I built my third PC while still in high school; however, it got used very little once I started university. This felt especially sad at the time since that third PC was the first where I could genuinely splurge. Ultimately, it was my first laptop that felt like my third PC since it got the most use due to my long days away from my room for classes, work, and study.

I started my mornings early with classes. In the afternoon, I worked as a computer repair tech. In the evenings, I had study sessions with friends at the library. Although I would give anything to have the same energy I did then, I remember that time felt like a dream. Part of it was due to a strong feeling of being on autopilot because I followed a prescribed path of classes and problems to solve. Although I enjoyed proving the formulas in Physics and Calculus, it was circuit building where things started to feel unbearably tedious.

Strangely, the classes most related to my specific major and those most like the tinkering I did as a kid were the ones I was most bored with. In contrast, I had another course where we worked with the C programming language, where I had a blast. I couldn't tell you why then, but now I'm sure it was due to the feedback loop. Solving circuit problems meant building the physical solution manually. With software, it came to life as fast as I could think/type it.

Even though I gave Electrical Engineering classes another chance the following semester, I soon changed my major to Computer Engineering. This allowed me to keep most of my credits while not leaving behind hardware altogether. With this combination, it wasn't long before my assignments meant staring at a terminal as I flashed custom firmware to microchips, much like when I was rooting phones.

Revisiting HTML

Coincidentally, the year I started as a Computer Engineering student was when I moved out on my own. Although I was paid well as a computer tech, I needed more money to make ends meet now that I had to account for rent and other living expenses.

This led me to look for work that I could do on campus to supplement my income. Initially, I worked in a bio-lab where I would mix and pour agar into petri dishes. This position was great since I had a key to the lab and could get the work done whenever I had a chance, as long as they weren't waiting on me. Unfortunately, this campus job had funding limits and had enrollment as a pre-requisite. I would need something else during the summers since I would work full-time to save extra money.

Fortunately, I found a CMS admin position a short time later. This job was still on campus but wasn't posted as a student job, so it didn't have those limits. However, this job also allowed me to work the hours I could as long as I completed my tasks. And so there I was, modifying HTML like I did as a kid, playing pranks on friends via MySpace.

Coming Full Circle

After all these significant changes, I felt like I had gone full circle. The same work that had made me extra money in high school was now making me extra money in university. Partly out of necessity but also through personal growth, I saw opportunities where I had previously turned my back. Eventually, these opportunities allowed me to leave my computer tech job and focus on being a developer, aligning my work with my studies and passions.

From my school work to my job to even the projects I would take on the side, the more I learned about software, the more I wanted to put it into practice. All of this culminated in my Bachelor's in Computer Engineering with years of experience as a software developer. Even my computer networking classes were a breeze because I had already been working with docker containers and other various deployment methods for real-world applications in the oil and gas industry through the job I held in my final year.

The tech stack I work with might change over the years, but I still catch glimpses of the same themes. For example, I've been able to lead projects where we migrated content to a new CMS platform and completely re-imagined front-ends. Through that project, I kept thinking about my first official developer job as a CMS admin, which kick-started me down this path in many ways.

Continuous Growth

There will likely be more cases like this where I revisit previous topics but with more experienced lenses. One thing is sure: I'll keep tinkering and creating the same way I always have. I've grown less attached to the medium and more to the process.

I plan to document some of my projects on my website to help others start down this path or actively grow in the same areas I am.