Pulling things back online for daily code has been interesting. Distractions, dumb bugs (where documentation is lacking), and not preparing for employees have been quite interesting.

Since last I wrote (gosh, that stuff looks dense), I’ve taken a job offer! It’s remote security work. So, - dishwashing; + remote security. Still waiting on the hand to heal up.

Initially I had concerns about their conflict of interest policy, given that I have 3 employees to pay for and will be setting up security to protect the product. Really, after talking with two of my mentors, I don’t think it’ll be a problem (slightly worried I’ve scared them off though).

Task-wise, it’s been a question of dividing things manageably, scheduling them, silencing notifications, and getting stuff done.

As far as digital sluff, It’s getting pretty minimal (thank goodness). The notes are getting reduced and I’ve only kept reference snippets (1.4mb). It’s mostly because I’d like quick notes on vue, django, postgis, shell, rust, and golang.

Honestly, getting those in a public reference document might be better.

okay. okay. bite-sized pieces. check the todoist list… automate something new once every day… k… blog helper script could use improving. Done.

recycling the digital docs mostly could be acheived by using yaml metadata. So let’s go with hug: true/false, and then I can run an indexing function on it. That could also be used for task tracking….

business-pitch wise, it’s been suggested that I cater to sysadmins more with the product, which is a different pitch from the linux-afficionato.

Failure Operations: “Open Source, Transparent, Durable, and Caring”

Desk Personal: “Less headaches from switching linux distros. Preferences where you want them.”

Desk Sysadmin: “Give users more control with less breaking.”