Member OP
Happy to help, I suppose. Monday 10:00 is the new target. I'll post photos of the labeling if anyone cares. Color code is:
The yellow was supposed to be orange but the supplier sent yellow. It works.
This is how standards die. One substitution at a time. In five years someone will be tracing cables wondering why storage is yellow and the answer is "supplier error, 2024."
Document it in the wiki. Future you will thank present you.
Wikis are where documentation goes to be outdated. I put network diagrams in Git, in the same repo as the Terraform. If the infrastructure changes, the diagram changes or the CI fails.
Weekend project: nothing. I already automated my documentation guilt.
Terraform is also where documentation goes to be outdated, just with more state files. I've seen modules with comments referencing instance types that don't exist anymore.
My weekend project: terraform state rm a resource that doesn't exist and pray.
Prayer is not a backup strategy. Neither is ZFS, but at least ZFS has checksums.
I'm going back to my garden beds. Dirt doesn't have state files.
Member
It does though. Soil composition, pH, moisture levels. I have a spreadsheet. Everything becomes a spreadsheet eventually.
Raised beds are built. Filled. Seeds in tomorrow. The server can wait.
Member
This thread has become a spreadsheet of human experience. We have servers, gardens, compile farms, and bathroom fans. The original question was "what are you working on this weekend?"
I am working on accepting that I will not finish chapter 3 of the Rust book. Again.
Chapter 3 is where the borrow checker wins. Everyone stalls there. My advice: write bad code that compiles, then make it good. The compiler is not your enemy, it's a very picky friend.
Weekend project: mentoring a junior through chapter 3. Pray for me.
This is the real work. Not the racks, not the labels, not the compile farms. Passing knowledge to someone who thinks 100 tick is just a number.
Good luck. Report back.
It is just a number. The kids playing Valorant don't care about tickrate because the game feels fine. We cared about CS 1.6 tickrate because it was all we had to optimize.
Progress is not caring about the things that used to matter.
