and honestly, one of the specifications that I’ve given myself for the completed projects is a full-on cheat code as well as a quick on-ramp for some hands-on-device testing throughout the projects lifetimes.
one of my requirements is that I want to be able to use the keyboard, trackball, and display of my personal computer to connect over VNC to remote computers. it absolutely requires a standards-compliant vnc protocol client program. so I’m gonna be on the hook to implement that. I haven’t written a vnc client yet, but when I get to that point I will; it’s a knowable spec to hit, and if I’m not planning on trying to impress anyone with it I can even skip the parts of the spec that I know I’m not gonna need for my use case.
smaller.
but then, I have the ability to lean on “old ways” by remoting into my current laptop and using its linux environment to do whatever it is I’m trying to do that my new personal computer system isn’t equipped to do yet, and every time I have to fire up the vnc client it’s an opportunity to identify an eventual TODO for me to get to so I can move my personal computering off of the current platforms and onto mine over time, at my pace, without any more artificial deadlines than necessary. gently, thoughtfully, exploring the possibilities for my personal computering.