Small adventure Monday reactivated

I’m getting a lot of invites for virtual events to listen to these days. For the most part, I try to place the invite on the calendar so that I remember to attend the event. Turning off all the notifications on my smartphone was an epicly good decision, but it does stop some prompts that would be useful. It does beneficially block a lot more distracting content than it surprises good content. 

I was looking at getting a bridge SILO humbucker from Bare Knuckle pickups [1]. 

Testing out YouTube Shorts has been interesting. The popularity window for something loaded into YouTube Shorts is mind bogglingly short. Based on the first 3 videos it seems like within a few minutes of launch it either takes off or it just fades along. 

I’m still on the waiting list for Langflow access [2].

Botpress was pretty easy to use. After login I clicked answer questions from websites to create a bot. I added both Civic Honors and my main Nels Lindahl domain. They just jumped in and advised me that the knowledge upload was complete. Publishing the bot is not as low friction as the Voiceflow embedding launch point, but it was not super hard to work with after you find the share button.

I messed around with the local installation of Flowise. 

My attention ended up moving over to learn more about LangChain in general [3].



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.