Getting into the swing of coding again

I opened my first issue on GitHub. The author responded to it, which was exciting. It’s distinctly possible that I’m going to fork that repository to have it do something a little bit different than what the author intended. My fork would be a depreciation of some pop up functionality to make the overall plugin easier to use for people who were just wanting to engage some direct links to other pages. One of the things that I’m seriously considering is just setting up a backlog and keeping interaction notes for my efforts. 

That made me wonder if GitHub kept a native backlog feature. Based on my initial searching it does not appear that GitHub has such a thing. My primary writing backlog is something that I keep in a Google Doc at the end of the document. Functionally, I work on one unit of writing a week so having a backlog of 5 items in planning and review and then tons of uncommitted items is not a very big deal. Working on a coding project is a different type of effort compared to that one unit a week writing project. I’m going to need a better way to manage my backlog or I’m not going to ever get to code complete as a single developer on the project. 

My current plan is that every day I’m going to try to spend an hour dedicated to building code either right before or after dinner. I have some detailed sketches of what needs to be built out and I’m working on building and coding it live in production. Some of the bigger elements of the project are probably going to need several hours of attention at one time to get set up. That will need to be a weekend activity to be sure. On the brighter side of things only a few of those types of large efforts exist.

I broke out the extra large notepad and started some sketches. My process is a little different from most people. All of the concepts and ideas normally get crunched in my head first and then I draw out the slides or the graphic after that process completes. It’s not an iterative sketching process when I build things out. The thing has been brought into existence before I try to memorialize it with a graphic.

Putting in the work on that backlog

This morning I dug into the content block that I had assigned to this weekend with reckless abandon. You may recall that recently I shifted my entire writing backlog to the right by about a year and added a new set of content to the queue instead. I’m currently working on those new blocks of content creation and it happens to be going pretty well so far. Within my current workflow I’m targeting some audio recording every Saturday Morning and working on content creation during both Saturday and Sunday. My goal of course is to complete one block of the backlog each week while considering the next 5 in the backlog. That functionally gets me ready to work on the next blocks of content by considering them before ever trying to write or research. That is an important part of the process. You sometimes have to think deeply about something before you try to write about it. 

A few general updates… 

  • Yesterday, I did update the weblog menu to remove a couple of the social network items from the top to streamline content delivery. 
  • I may at some point just remove the GitHub link as well. That one remained, but it is possible that it may get removed here in the next 30 days. That is something that is being considered. 
  • The homepage is back to the about content instead of showing current weblog posts as well. I’m not sure if that is going to be a permanent solution to the homepage. It’s pretty easy to get to the posts section and nothing would stop somebody from reading them in order if that old school blog experience was desired. 
  • I’m considering converting my entire writing collection into a corpus for model training again. It has been a couple years since the content was converted into a corpus like file for model training. The last time was for use with GPT2 about 3 years ago.