Professional Max's Newfound Life in Tech

    If, for no one else, this post may wind up mostly for me. In that, I'm not trying to use it to communicate new information to you; I'm trying to keep track for myself, as a reference, a set of steps I've been instructed to take by another blog post . But, if it's not for other folks to read, why publish it at all? Well, the honest answer is: I also hope it can positively show my workflow, etc, in case someone else is looking to inspect my skills. Because, you see, it was a potential employer who sent me down this rabbit hole. Time to put my thinking cap on.     I should take a step back. In general, since my time in FlatIron School's Software Engineering Course, I have been really eager to keep my "backend" skills sharp, and been searching equally for "Frontend","Full Stack" and "Backend" entry level positions. Then, a company with a backend position got back to me :o     But, their Technical Interview is not at all what I

    Hello, my loyal fans. Good news from my world - tomorrow I'm starting not just a new job, but a new (to me)  kind of job: I'm going to be a tutor! In this case, specifically, I'm going to be a Coding Tutor. And, even more specifically, I'm going to tutor Elementary School kids.     But (and this is the twist): I'm not going to be tutoring them in Javascript, HTML, CSS or the other languages I learned at the FlatIron School. I'm going to teach them a language specifically meant as an introduction to the possibilities of code; a language that works on a much more visual/click-and-drag basis, as a way of getting kids excited about the possibilities that coding can unlock. I'm talking about Scratch . Aww, lookit that cute cat     On first introduction, the language surprised me, or even made me skeptical, as something worth learning. Allegorically speaking, I have an abundance of fond memories playing on the software KidPix when I was a child, but in no way