So, what’s this all about? Well, I’ve been learning to code off and on for at least a couple of years already. But despite my best intentions, it has been more a case of ‘off’ than ‘on’, what with life keeping me busy. As someone with a family, a career, post-grad studies, and a long commute (in pre-Covid times at least), it happens to the best of us. And me.
Turns out that the answer is… yes. It does. Or to frame the answer better – I need another learn to code blog. For myself. To keep my own progress moving forward. To write about what I learned, to better solidify that knowledge. And if you want to join me on this journey? Great! The more the merrier, I feel. I look forward to meeting all of you!
It’s not a case of me not blogging at all – I launched a blog a couple of weeks ago looking into tech solutions to climate and conservation issues, given that I find the topic fascinating. And I’m thoroughly enjoying that. However, given that the site is branded and marketed as focusing on the aforementioned climate tech content, I’d prefer to keep it that way. I’d rather not dilute that site’s focus, if you will.
This blog, however, is my space to write about a far greater scope of code-related topics. A place where I can write anything from “Why I like commenting descriptions out in HTML” to “Lookit! I made a Flexbox thingy that MOVES!” to “How to use Docker on Beast Mode”.
Can I be honest? I really have no idea what Docker is. I read their description but there were lots of really long words that mean very little to me as of right now. That will change. That’s the point of this blog – documenting that change. I look forward to actually having an idea of what “OS-level virtualization” even means. We’ll get there. Baby steps.
So, I hope you’ll tag along for the ride. And please stop by on Twitter to say Hi!
Until the next time!