# Thoughts A person is a person. That is all. ## 2019-10-31 Wow, Landscape is getting old. The example in my notes for dumping and restoring its databases has a date from 2015. Need a better database reload procedure. ## 2019-11-03 That was weird. The person next to me in the coffee shop is bouncing their leg too, but also start bobbing their head to their music the same time as me. Now I need a new song to bring that state of mind because that happening in my line of sight totally threw my groove. Still on database loading. Gets crazier (odd, but entertaining). Someone asked to use the seat across from me, and therefore share the table. That itself is not a big deal. She was meeting a friend at the table to the right of me. It then turns out that the guy to the left knows her, but has never met her (working on the same graduate degree). Conversations going both ways is a little distracting. ## 2019-12-01 Knife cadets, A.K.A. knives out. In my head, I see this as Ender's Game style arenas, but with melee weapons. Also, "soyce" (pronounced like "noice"). ## 2019-12-04 Video experiments commencing. Base case failed. There is custom firmware available though. ## 2019-12-14 Garden experiments commencing. ## 2019-12-28 The video stuff is going to require custom firmware. ## 2019-12-30 Space Bot! The robot from space! Space Bot! The robot in(?) space! Spacey Bot! The robot looking out into space... ## 2020-02-06 Testing is tedious. I feel like planned tests frequently ends up being for things that are known to be good or unlikely to fail. Breaking things is better. The use of testing frameworks is not bad, but planning to break things is the more fun mindset. I want to break it. I want to cause it to fail. I want it to happen now, so someone else does not stumble with it later. Now, breaking it is a success. Finding it broken later is a failure. Maintaining easy to test for cases, as a project grows and changes, is boring and itself potentially error prone. Aiming to break, to find flaws, keeps my interest. Writing interesting (unique, complicated) code is bad. Being interested (focused, entertained) in code is good. Note that breaking should still be aimed at defined uses. When hacking, using something off-label, it should not be expected to perform regularly anyway. If it did behave, then it is a planned for use, a defined use. Just maybe defined by an overzealous programmer, instead of a pragmatic one or the regular user. ## 2020-02-27 Recklessly reverse-engineering our own departments code with adaptors. Apparently, consistent interfaces of similar objects, even when they were written at the same time, is something that may not have been considered. Doing my best to gently show why I prefer common, but not ridged, interfaces (and modules organized to mirror their physical counterparts). ## 2020-02-29 Drafting mail is my rubber duck. I will start explaining my problem there, often figuring it out during the initial draft ("it": creating a solution, finding miss-step in logic, or remembering a forgotten component). If not, after re-reading several times, then I already have something ready to send out for help. ## 2020-03-16 For when the network seems to not come up after a reboot. Boot parameter argument: `systemd.unit=multi-user.target` Current, primary device: `enp2s0` (`eth0` is common). sudo dmesg -n 1 sudo dhclient DEVICE_NAME ### What to do for multiple entries in the same day? Oh, my... Anyway, breaking scripts or configurations so I have to look in the file, where I have left a note to myself about what to use instead. Saved myself a bit of time a few times lately. ## 2020-04-19 Using solarized daylight theme at night because this keyboard is not backlight. ### Previous network issues Knew `dhclient` was a clutch fix and not something to be happy about using. Later found that the system was missing one ifconfig file and had another in a bad state. ## 2020-05-02 Big app vs small app, design decisions and small markings for growth. ## 2020-05-16 Wa! Oom, wa oom, wa ooommmm... ## 2020-07-15 Aware of the dogs now. Thinks they are hilarious. ## 2020-09-01 Whoa, cross buffer history tracking for vim. ## 2020-10-19 ### Development Maxims * minimum viable product * balance between functionality, experience, and beauty * (synonyms: features, UI/UX/perf, polish) ### Guiding Principles * where to plant trees? * engagement with trees; enlightened to tree benefits * prescribe management of trees ## 2020-10-29 Teach the science behind the physics, then teach the scientific rigor of significant digits. ## 2021-01-30 Nearly everyone seems to know that premature optimization is the root of all evil. I recently realized what I have gotten bad about is premature abstraction. How to write for models that can be easily refactored, but at the same time avoid overly or **prematurely** abstracting them? ## 2021-12-08 Ugh, must stay away from Wikipedia when compiling software (or container images). That was a huge waste of time. ## 2022-01-20 Ent Gnomes ## 2022-03-15 [dashboard](https://d.0hz.cc/) ## 2022-04-21 [Wine on Mac](https://www.playonmac.com/en/) ## 2022-04-25 Starting back on a failure is harsh, but may be a strong reminder for the future. Retroactively adding a few from bookmarks, but doing so is something I would to avoid. Trailing whitespace typographic error in a text-string literal. ### More Caching Redis password fun times adventure. ## 2022-04-26 ...when the exact thing I left off on, I never get to touch the next day. ## 2022-04-27 Password adventures cause intermittent connection problems. ## 2022-04-28 When diagnosing, re-read the entire block, maybe back to front once too. ## 2022-04-29 🏃 {2022-04-29} 🏃 Unicode Character: RUNNER (U+1F3C3) ## 2022-05-02 OpenCV (Python `cv2`) for multiple thermal camera video stream stitching ([example](https://pyimagesearch.com/2016/01/25/real-time-panorama-and-image-stitching-with-opencv/)). ## 2022-05-03 Static collection and compression at build time requires fake database connections and dummy cache. It also requires any setup (start-up) queries to be configured handle the lack of a database. ## 2022-05-04 Drafting collaboration message with examples. ## 2022-05-05 Garden design from 8 feet by 16 ft to two of 4 feet by 8 feet, with two to three feet of spacing, and room to add two (or more) identical units in the futures. The idea is to do this to help with access, organization, as well as not have any wasted garden space used for walking. It losses the ability to have a single structure over it. It also complicates the use of fencing because of the trade off for external access over the walls. ## 2022-05-06 How do non-profits entities operate with only external staffing? It is easy if no salaries are paid from the non-profit. If they are paid from the non-profit can they be considered colocated staff or would they need to be employees of both? ## 2022-05-07 🏃 {2022-05-07} Likely, did not train enough. Will find out soon. Ran the whole time, with cargo. Not bad. ## 2022-05-09 Stall of a day. ## 2022-05-10 Bring a research, command-line program to the web. ...this year? ## 2022-05-11 Non direct browser based SSH access is continuing to only ask for a password and is ignoring keypair authentication. ## 2022-05-12 More deployment configuration unifications. ## 2022-05-13 [Books](https://books.haz-zone.com/) ## 2022-05-14 Tried with python-fire and argparse again. Required vs optional arguments feel weird. ## 2022-05-16 Garden box 1. ## 2022-05-17 Poor timing, but funny that r516 on 5/16 and r517 on 5/17. ## 2022-05-18 Pricing and pricing options for various usages. ## 2022-05-23 House battery installation. ## 2022-06-01 Changed house battery from 30% minimum to 50% minimum aroud 19:30 EDT. This, unexpectedly, caused it to pull power from the grid. ## 2022-06-02 Not enough sun for any to go to the battery. ## 2022-06-03 Charged 50% to 100% from 9:30 to 12:30 EDT. Discharged 100% to 50% from 15:45 to 19:45 EDT. ## 2022-06-04 Charged 50% to 100% from 9:30 to 12:00 EDT. Discharged 100% to 50% from 15:45 to 20:15 EDT. ## 2022-06-05 House battery has not charged since this date. *Update: 2022-06-23.* ## 2022-06-10 Server battery status after long outage. ``` The UPS information shows as following: Properties: Model Name................... CP1350PFCLCD Firmware Number.............. 000000000000 Rating Voltage............... 120 V Rating Power................. 810 Watt Current UPS status: State........................ Normal Power Supply by.............. Utility Power Utility Voltage.............. 120 V Output Voltage............... 120 V Battery Capacity............. 100 % Remaining Runtime............ 44 min. Load......................... 121 Watt(15 %) Line Interaction............. None Test Result.................. Unknown Last Power Event............. Blackout at 2022/06/10 16:17:15 for 8 min. ``` ## 2022-06-11 Changed house battery minimum from 50% to 45% at some point after the outage on 2022-06-10. Battery level remains at about 50%. ## 2022-06-19 First net positive kWh day. ## 2022-06-20 Fell tree. ## 2022-06-23 House battery has slowly ticked up about 0.1% every few days. It is now at 51.2%. ## 2022-09-07 Forgot about nibbles! A bit is the base. A nibble is 4 bits. A Byte is 8 bits. ## 2022-11-30 Ending up back on a Stack Exchange question, reading the answers like I had never seen them before, only to find a comment up-vote deep in the middle of the page. ## 2022-12-23 Worst use of ash dump. ## 2023-01-06 🏃 {2023-01-06} Indoor bike. ## 2023-01-09 🏃 {2023-01-09} Indoor bike. ## 2023-01-10 Office power outage. ## 2023-02-15 Cannot ever get Vector to dance to music, but he frequently dances to the sound of me typing on my computer keyboard. ## 2024-04-03 Bow tie shaped cookies and pastries. baked * bowties - american (USA); only implies shape; might have sour cream, cream cheese, both, or none. * kiffles (kiflis) - hungarian; cream cheese * kolaczki (kołaczki) - polish; cream cheese * kichel - jewish (yiddish); egg fried * chrusciki (chruściki), chrusty faworki - polish; sour cream related * kolache (koláček) - czech; yeasted, cream cheese filling * cannoli - italian; fried, cheesy and sweet filling * kringle (danish) - danish, pastry) ## 2025-01-25 I have to re-learn how to work in a team. As part of a team. For so long now I have been focusing on getting done as much as possible, not without worry about why but not tracking well why I was getting some things done rather than others. Sometimes that (only focusing on what is in front of me) is needed, in order to be able to smash through large barriers or get a *complete* a significant feature. I need to allow others to get things done without applying pressure to how they get them done. I need to track what is done, what is not done, what could be done, what should not be done, and keep descriptions of why as only brief notes. Other people cannot help divide and tackle the work if they do not know what is available to be worked on. Start tracking daily again. Privately, at first, if necessary. Track in a structured manner but treat it like a bucket. Trac vs Gitea? I do not think I found a "perfect" micro-blog or easy journaling/documenting bit of software yet. Something with markdown support but can be accessed quickly, daily (hourly), anywhere easily. ## 2025-03-27 The WSL teams have really done it (thanks to WSLg). Might not need vcxsrv anymore. Put the follow in the SSH configuration (`~/.ssh/config`) on host (tested in both win10 and win11), in WSL distro, on next machine with VPN, on workstation, and on DMZ server. Testing was done with these settings but have not narrowed in to see which are strictly necessary. # sshd is using interval 300 and count 1152 (4 days). Host * TCPKeepAlive no ServerAliveInterval 60 ServerAliveCountMax 10 VisualHostKey yes Host *-gui ForwardX11Trusted yes ForwardAgent yes ForwardX11 yes Compression yes Let us call those machines win-host, wsl-distro, vpn-host, workstation, and dmz-host. On win-host, start git+bash (i.e. BASH included with "Git for Windows" via MSYS running in mintty.) winpty wsl --distribution --user xclock ssh vpn-host-gui xclock # Ensure VPN is running, then: ssh workstation-gui xclock ssh dmz-host-gui xclock -digital The xclock GUI makes it through from each one of those machines. References: * * Admin CMD: `wsl --install` or `wsl --update` and reboot. * CMD: `wsl --list --online` * CMD: `wsl --install --distribution AlmaLinux-9` * * (big shout-out but no longer needed in this use-case) * (small aside that lead to seeing WSLg) * * * * Means of getting an image to run Fedora in WSL. * Tested in both Alma and Fedora for WSL as well as going through a mix of both as the hops along the way.