Hello there! Rob Green here and this is my part of the web!

I’m not too sure what I’ll make of this site, but as of Fall 2023, it’s going to start off as a blog and area to share my self-taught journey into the realm of Software Engineering and Machine Learning. Maybe one day I’ll add some recipes because I love to cook and experiment, or maybe add some travel/camping because I love to adventure and explore so instead of naming the website:

which I know is a great website name that just easily rolls off the tongue, I went with GreenGuy.me which is a little more generic.

So a little about my professional life… I have a Bachelor’s and a Master’s Degree in Mechanical Engineering and have had a career in this discipline for 7 years. When I was going into post-secondary school I decided not to go into Software Engineering because I told myself “I don’t want to work sitting at a desk my whole career” even though I was quite good at programming in High School and really loved it. So since I was good with my hands and fairly creative I went into Mechanical Engineering thinking I’d one day invent and build great things to help people. Ironically however, thanks to my love of design which allowed me to pursue my creative side, I ended up behind a desk as a designer…

(At least me mum thought I was smrt)

…a designer that constantly utilized programming to automate all those boring repetitive tasks and greatly speed up the design process. I found myself programming often in every role I was in; I just seemed to always gravitate towards it and find solutions to problems using those skills. Key examples in each of my major roles are below if you’re curious.

1st Year University Co-op

3rd Year University Internship

First Real Mechanical Engineering Job

Opto-Mechanical Design Engineer

If you did check out the above examples you may have noticed a general theme where I utilized my foundational programming skill for my company to learn their tools available and then create something that ultimately made the company no longer need to hire additional employees as they grew. I believe I was an under appreciated asset partly because my superiors didn’t understand the extra work I was doing above my job description and I never really got any appreciation for it; however, I knew I must be valuable if my efforts made hiring of new employees no longer required. Even with loving both programming and solving problems using it, there was something else I really admired about it compared to mechanical design. When attempting to design a new physical product or solution to a problem there is always the prototyping and testing phase. Many project managers didn’t seem to understand this part and for reasons I still can’t understand they expected initial designs/solutions to work first try. I was often either setup for failure by being forced into building that initial CAD design straight into production (which obviously never worked first try – well, maybe once) or I had to spend many frustrating hours trying to convince them to spend some project money on tests/prototyping. In fact, I often found myself spending more time doing this than actually doing design work and that combined with so much red-tape to actually get anything done at all made me really dislike my career choice. In programming/software this barely exists. You may have dev sever copies to test with or the only barrier between your potential solution and seeing if it worked for that juicy job fulfillment is just clicking the Run button. Therefore, I was always excited to be programming on the side and able to get solutions to problems working without spending a week making stupid presentations and calling meetings to prove why we needed to spend $100 and a couple hours testing some off the shelf parts. In fact, even when approved it took weeks to actually get the same-day shipped part as it made its way through the full purchasing system. That’s just frustrating and not enjoyable at all.

After a series of unfortunate events which I’ll refrain from sharing here, I was essentially forced to quit my opto-mechanical design job. This created an opportunity to really think about my career and if I wanted to continue to pursue it. I realized that the most enjoyable parts of my career was finding inefficiencies to automate and any of the programming I learned in order to accomplish it. And so here I am teaching myself one of the most interesting topics to be able to automate very complex tasks: Machine Learning. I believe life is too short to spend a considerable portion of it in a career you do not fully enjoy and that it’s never too late to change paths once you realize this. So join me on this new career path of mine as I put this theory to the test.