Intro to Linux: How I Stayed in the Dev Game While Too Broke to Buy a PC

My first full-time development job was at DocWorks, and I was surrounded by developers with computer science degrees, certifications, formal training. I was self-taught. One colleague there was deep into hacker culture, had his CCNA, had done time in local computer shops. He introduced me to Ubuntu. Showed me the graphical interface, probably right around the transition from Unity to GNOME. That was the first time I saw Linux as something a regular person could just install and use. I was a Windows guy, too broke for a Mac, and up until that point my only exposure to Linux was vague references in movies and hacker culture.

The Colleague Who Gatekept Everything

I didn't learn much from him. He was the type to gatekeep information, send you down rabbit holes, and let you waste time figuring out things he could have explained in two minutes. His name was Justin. He was finishing a master's degree and seemed like he'd have job offers lined up, but his personality made him impossible to learn from. He bragged about students failing his classes like it was a badge of honor. Teaching is a skill, and he didn't have it.

Fast forward a year or two, I got fired from DocWorks. Bad decision on both sides. What happened was they pitted me against Justin and asked if I could take over his role. I didn't feel confident enough to say yes. I didn't want to throw him under the bus. In retrospect, I should have just asserted myself. It was about confidence, not evidence.

Getting fired turned out to be a blessing. I avoided entrenching bad habits from DocWorks' dysfunctional "Franken system." The place gave me real experience with databases, servers, APIs, HIPAA compliance, but the codebase was a mess, and staying longer would have cemented bad patterns. I would've become a lifer stuck in a poorly architected startup.

Cable Tech and Customer Service

I moved to contract work as a cable technician, installing modems and setting up internet for people. That job taught me things I didn't expect to need: customer service, effort estimation, how to translate technical solutions into terms a customer actually understands. Those skills ended up complementing my tech growth in ways I couldn't have predicted at the time.

The Old XP Machine That Changed Everything

My real Linux breakthrough came after DocWorks. I had this old Windows XP machine. Microsoft had stopped security updates around 2012, 2013. The thing was end-of-life, nearly unusable, crashing constantly from years of bloatware. I couldn't afford a new computer.

So I installed Ubuntu.

It revived the machine. Linux is lightweight. Minimal default software. It freed up resources that Windows had been choking on for years. That computer got three more years of life out of it. Using Ubuntu as my primary workstation forced me to learn Bash, command-line operations, file management, package management with apt, networking. It felt like magic, turning a dead machine into a functional development environment.

How It Shaped Everything After

That Linux proficiency changed my career path. When I started picking up contract development work, I could actually claim Linux experience on paper. That led to roles managing servers, and eventually pushed me toward cloud architecture. The whole thing started because I was too broke to buy a new PC and installed Ubuntu out of necessity. That necessity pointed me toward full-stack development and cloud work, and Linux became a core part of how I operate professionally.