u/hakai-time

if you're new and the knife still feels dull after a bunch of passes, try this before ordering a coarser stone:

1. color the bevel all the way to the edge with a sharpie.

2. make 3-5 light passes per side at the angle you were already using.

3. look where the marker came off.

marker gone near the shoulder but still black at the apex = too shallow.

marker gone at the apex but black behind it = too steep.

marker gone across the bevel = angle is close enough, now work until you can actually feel a burr.

takes less than a minute and it tells you if the problem is angle/contact, or if you just haven't spent enough time on the first side. way better than counting strokes.

small ONI habit that saves a lot of dumb rebuilds:

when something "isn't working", click the building and look at errands before you place a second one.

coal gen empty? see who can actually supply it. grill idle? check if the cook is walking across the map for ingredients. algae diffuser off? maybe nobody can reach the algae or the priority is buried. ranch starving? delivery/drop-off can be the bottleneck, not the room. refinery stuck? one blocked liquid/supply errand can freeze the whole chain.

adding another grill/generator/diffuser often just gives you two empty buildings. the errands tab tells you if the real issue is supply, access, priority, or power.

when a used record sounds rough, I try to separate the problem before cleaning it five times or buying another copy.

• same tick in the same spot every spin: scratch or groove damage
• random crackle that changes after a wet clean: dirt or static was part of it
• fuzzy vocals mostly near the last track on a side: check alignment and tracking force before blaming the record
• one channel fuzzier than the other: stylus, alignment, or azimuth before buying a duplicate
• every record gets harsher after 15 to 20 mins: clean the stylus and check tracking force

the useful test is comparing two records in the same spot: one cheap clean record you know well, then the problem copy. if both get ugly near the inner grooves, its probably setup. if only one copy does it in the same place every time, that record may just be cooked.

small thing that saved me a lot of head scratching: when reaper suddenly starts copying stuff wrong or moving things i didnt touch, i check these before digging through prefs.

• ripple editing: easy to leave on and then a paste moves half the project
• envelope points move with media items: great when you want it, annoying when automation follows every copied clip
• auto-crossfade: if tiny fades keep appearing, this is usually why
• item mix behavior: decides whether overlapping items replace each other or stack
• midi editor grid: the ruler can say beats while the grid is still set to 1/32 or something weird
• preserve pitch when changing playrate: good to check if speed changes dont sound how you expect

not really a setup guide. just the short sanity check i wish i had earlier before assuming a session or plugin was broken.

a new service feels obvious on install day. six months later you remember the app name and forget the ports, paths, login and backup job.

for each service id keep one plain text note with:

• what it does and who uses it
• hostname, ports, compose path and volume paths
• which password manager entry holds the admin login and secrets
• what gets backed up, plus one restore command you tested
• update steps and the last version that worked
• what to remove if you retire the service

store the note beside the compose file. if the container will not start, you still have the paths and restore command.

write it while the setup is fresh, then update the note whenever the config changes.

10gbe is fun. it also doesnt make every file copy 10x faster.

before buying nics, switches and transceivers, id test one real transfer and watch:

• disk speed on both ends. one hard drive will usually run out of steam long before a 10gbe link
• cpu use during smb/nfs transfers, especially on little boxes
• pcie lane width for the nic. some mini pc adapters look right but run on fewer lanes
• the client too. a fast nas feeding a laptop over wifi is still a wifi transfer
• temps on sfp+ modules and tiny pcs after 15 to 20 mins, not just at idle
• whether one fast link to the nas fixes the problem, or if every box really needs 10gbe

iperf3 tells you if the network is fast. copying the same big file both ways tells you if the whole path is fast.

finding the actual slow part first is way cheaper than upgrading every box and still seeing the same 180 MB/s.

use masking tape and give each connection a number: 1 on the cable, 1 beside the port, then 2, 3, etc. the photo is backup for weird ports and power bricks that all look the same.

this takes maybe two mins before a move, repair, or deep clean and saves the dumb guessing game when everything goes back together.

Why YSK: a cable label is only useful if you know both what the cable is and exactly where it came from. marking both ends plus keeping one photo makes rebuilding the setup faster and avoids mixing up similar-looking cables or adapters.

leave the first page blank and number pages only when they turn useful. when something is worth finding again, add one line up front: 12 - seed starts, 27 - packing list, 41 - ink tests.

it keeps a messy catch-all notebook searchable without turning it into a full bullet journal setup.

everyone loves the huge rack pics, but if you're starting out, id honestly build the boring version first.

my starter checklist would be:

• one box you can leave on 24/7 without hating the noise/power draw
• write down the boring access stuff: ip, hostname, where passwords live, and how to get in if dns breaks
• one service you actually use every week. uptime kuma, immich, jellyfin, home assistant, wiki, whatever
• backups before anything important goes on it. then restore one file/photo for real, not just "backup job says green"
• a tiny notes page with ports, vlans, disk layout, and "how I rebuild this if the boot drive dies"
• only buy the rack/switch/10g stuff after you know what problem its fixing

the pretty labs are cool, but the lab that survives a reboot, power blip, or dumb saturday mistake is way nicer to live with.