Forum-style hobby notes for drones, 3D printing, laser engraving, webpage design, server hosting, ChatGPT vs Gemini, Proxmox, Linux, and maker workflows.
A public-safe knowledge base for the things I actually enjoy learning, testing, fixing, building, flying, hosting, printing, engraving, and comparing.
Check props, battery, firmware warnings, GPS lock, wind, line of sight, return-to-home altitude, and landing zone before launch.
Carry spare props, charged batteries, SD cards, landing pad, lens cloth, USB cable, power bank, sun shade, and a simple paper checklist.
When chasing a bad print, change only one thing: bed level, Z offset, flow, temperature, speed, cooling, or retraction.
Layer direction matters. Rotate parts so stress does not split layer lines, then tune wall count, infill, material, and temperature.
Before engraving a final piece, run a speed/power test grid on the same material. Focus, ventilation, and masking matter.
Wood, acrylic, leather, coated metal, and glass all behave differently. Keep a settings log for every material and finish.
Give visitors obvious paths: who you are, what you make, where to watch, where to join, and what knowledge base to browse.
For a personal homepage, static HTML/CSS can be faster, easier to host, harder to break, and simpler to back up than a heavy frontend app.
Give each site its own Nginx block, web root, logs, and backup. Avoid mixing personal pages with app domains.
Before changing a live static site, copy the current index with a timestamp. Fast rollback beats panic troubleshooting.
Compare tools by task: coding help, writing, research, image reasoning, long context, integrations, privacy needs, and how well it follows instructions.
State the goal, current files, error output, constraints, and what not to touch. The more precise the mission, the better the result.
Snapshots are great for quick rollback, but real backups need separate storage, a schedule, and restore testing.
Use clear names for pools, bridges, VLANs, disks, and backup targets. Future troubleshooting gets easier when labels explain intent.
Open an alternate terminal, confirm the shell still works, then repair the default app instead of assuming the whole system is broken.
If Nginx returns 403, check that index.html exists, parent folders are executable, and files are readable by the web user.