Ever since I can remember I've been absolutely amazed by computers. When I was a kid my parents got a P.C primarily to check email. I don't remember what model it was, all I know is that it was a Gateway machine... and it was loud. My sister and I would fight over who got to use it, but whenever I got the chance I'd hop on and see what it had to offer. It was the mid-to-late 90s and we were rocking dial-up internet. My parents only had one phone line and ran a business so internet usage was restricted to odd hours on the weekend. Since internet usage was so limited I spent my time exploring the operating system and programs that were installed by default. This might seem boring to most people but I was in awe of the idea that something that isn't "real" could be interacted with and cause "real" results (opening the CD tray, etc). At this point I was pretty young (born in 92), and I had nobody in my life to explain anything to me about this mystery machine; I pretty much just observed and learned behavior. As I got older I eventually got my own computer (a Dell!) and eventually, when I was 14, we got internet that was slightly better than dial-up! Woohoo! At this point I was browsing IRC channels and web forums for this crazy thing called linux and taking in as much online time that I could. Eventually I met someone on a chat that told be about a cool new operating system called Sabayon Linux. Without hesitation I downloaded an image, wiped my desktop, and was greeted by a whole new world... a world of missing ethernet drivers... "What do you mean drivers?" I thought as anxiety pulsed through me. I decided that I could probably figure everything out if I just calmed down and hopped on my parents machine. Armed with a fresh cold Coca Cola while the sun set over the lake I set out on an epic adventure to find these damned drivers. Hours went by, and after many trips back and fourth to my P.C to get more information about what was required I eventually got ethernet working. I felt like a God.
I won't bore you with anymore details about how I learned from making reckless mistakes. I just wanted to drop this all in to explain how I learned at a young age that its okay to break things because you'll learn more along the way as you fix them. Eventually in High School I was able to take Visual Basic and a variety of Computer courses. I found my true love. Technology. I got to spend an hour every day during my senior year working with I.T to fix school computers, so it was natural to me that when I was told I had to go to college that I did something with technology. At this point in my life I could math, but I didn't like it all that much. With that in mind I signed up for a degree in Computer Networking. To keep things brief..
0. I enrolled in the Computer Networking program.
1. I got a job in I.T at the University.
2. I took an A.I class for fun and realized that the first 2 years of school were cool, but Computer Science was what I needed.. math wasn't bad enough to keep me away.
3. At the same time as the A.I class I took a full time job at the University so they'd pay for my schooling.
4. I got moved to an Administrator in I.T.
5. I left the moment I got my degree to become a Software Engineer.
Thanks to all those years of working in I.T and taking CN/CS classes I'm pretty well rounded in my knowledge of the once mysterious computer systems. I can pretty much do anything from writing Assembly code to wiring up and configuring a network from scratch... I just.. I'd prefer writing code.
The first "real" software job
I'm currently working (April 2019) at the first job that I got as a software developer. My official role is Computer Engineer because of a whole slew of reasons, but everyday I'm writing software and integrating various pieces of hardware in our systems integration lab. I would love to go on and discuss all of the cool things I get to do, but I'm not allowed to talk about it at all! Everything is always so damn secret with my employer, but what I can say is that I write C/C++ for linux and embedded environments. I work in/on vehicles, but they're vehicles that members of the general public will never get to touch or (probably) ever see the insides of. I absolutely love my job and my coworkers.
Due to the fact that my employer doesn't like me saying who I work for or what I do, I figured that writing about software and my side adventures would be a great way to show what I can do, and what I'm learning.
Yeah that is it. That is me and what I'm doing. I know I'm a terrible writer, if its not technical I end up going off on tangents and stringing random things together. Hopefully everything here made enough sense to whoever decided to actually read it, and hopefully using this as a platform I will be able to hone my writing skills and share some interesting tid-bits.