A video tutorial on git checkout with the patch option
How I use git to give better code presentations
I originally posted this on medium. The basic idea is the same, but I have done quite a bit of editing and added some content.
For years, I would live code while teaching development classes. The mistakes I made (and there were plenty) would lead to ad-hoc lessons on debugging, and that was a good thing. I had the advantage of time and being in an interactive classroom environment, was able to turn these mistakes into lessons. I built enough time into my lesson plans to account for the live coding, and the subsequent debugging, questions, and conversations that came with it.
I like writing code and building applications, but I’d like to focus those efforts on new and interesting projects, not on building and maintaining yet another blogging engine. So, when I started this blog, I decided to go with a static site generator. I am using Hugo, and after about six months, I am very happy with that decision. One of the things I knew when I started this blog, was that if publishing were to become too cumbersome or time consuming, I would be even less likely to write on a regular basis - publishing regularly is hard enough for me without my tools getting in the way.
UPDATE: The bins linked here were broken due to a major overhaul of webpackbin. I have recreated the bins, and the lessons still apply, but the versions of Motorcycle and Most being used are outdated. To use more current version, these code samples will need to be adjusted. In my previous post, I walked through the missteps that lead me to adjust my thinking about how to handle data in MotorcycleJS and CycleJS.
UPDATE: The bins linked here were broken due to a major overhaul of webpackbin. I have recreated the bins, and the lessons still apply, but the versions of Motorcycle and Most being used are outdated. To use more current version, these code samples will need to be adjusted. I have been playing with the CycleJS and it’s sister project, MotorcycleJS for the past couple of weeks and I recently decided to use my goto approach for learning something new so I could gain a deeper level of understanding.
I spent years as a technical trainer and as a result, I spent a lot of my time learning new things and also figuring out how to explain those things to people with less experience. At the beginning, I would spend a lot of time learning the new language, tool or framework and then I would go about figuring out how I wanted to approach teaching it. As I got more experience with both teaching and with learning new things, I found that I was able to combine these efforts.
People like to say the grass isn’t always greener on the other side. Those people are right, it isn’t always greener. Sometimes, however, it is actually greener. Here’s the thing about greener grass… it’s still grass. If you want the grass to stay green, you need to fertilize it, water it and manage the weeds so they can’t take over. When it gets long, you still need to cut it.
Ever have a
git rebase go wrong? Maybe you had merge conflicts and you missed something, but now that you’ve completed the
rebase, it’s hard to tell where things went wrong. Sometimes, in a situation like this, your best bet is to get back to a point before you started the
rebase operation. Well, I have to tell you, it’s actually pretty easy.
In my constant search for ways to be more productive and make my life easier, I discovered the Bullet Journal system, and now that I’ve spent some time with it, I’m loving it. I’m pretty sure I’m done looking for a digital solution for my day-to-day task management and event logging needs. Let me tell you why.
Part 6 of the video tutorial series covering RiotJS and Redux