Learning Log: Tracking Daily Progress
I’ve done a fairly good job keeping up with my commitment to documenting my daily learning! The workflow I’m using (write Markdown notes in Hugo notebook -> refine and post on main site) has been working well.
I missed an entry for Monday, February 5 but I also found that I didn’t spend as much time reading and going through things. One thing that is nice about this is that it’ll document the ebbs and flows in my daily learning and knowledge gathering/sharing.
There are a few other things that have been on my radar as well, which are listed below:
This article contained a link to another solid article about the recent changes in JS:
Micro product launches == developer therapy article by Trevor Ewen, on Medium
I read this article earlier about the author’s experiences launching an app created during a two weekend hackathon. There were some solid insights about the importance of clear goals and working toward implementing crucial features in order to ship something on time. This also mentions leveraging helpful tools to speed up the process of developing and shipping an MVP. Great read.
Homebrew Website Club: Insights
We had a great Homebrew Website Club](https://indieweb.org/Homebrew_Website_Club#Baltimore) tonight with lots of excellent discussion. As always, I learn lots from our conversation and insights and so it makes sense to add these to this writeup! Marty documented our notes here, but I wanted to share my perspective on some things I learned tonight, or things that I’m motivated to further explore.
Marty did some awesome things with Neocities, and it makes me even more excited to try it out and see if it’s something I can recommend to people looking for a quick portal to a web presence. Glitch continues to fascinate me. I’m very interested to learn more about it since it offers an extremely useful and valuable service. This is definitely at the top of the list of things on my radar!
We talked a lot about Hugo and the drawbacks that come from it being so incredibly freeform. There is such a level of nuance in the way that each theme relates to content, and this has a consequence of certain things being rather opinionated about how content is organized. I talked with Adam about my Hugo development -> production workflow and we discussed some different ways for doing this. I write all of my notebook content locally, push it to a remote production repo, and then my server has a hook that grabs it and builds the site and serves it. In the past, I’ve loved this workflow and want to emulate it with my general WordPress development.
Daniel Shiffman – Coding Train video on Classes
That’s all for now! I’ll be posting more as I continue to write. This workflow seems to work well for me so far. Some of my entries will be more refined and complete than others, but my goal is to start with my notebook where it makes sense and then transfer to my main WordPress site after refinement.