• 0 Posts
  • 25 Comments
Joined 11 months ago
cake
Cake day: December 22nd, 2023

help-circle








  • as a chronic documentation reader, the best advice i can give is to document everything Anything that the user can and will potentially interact with, should be extensively documented, including syntax and behavior. Write it like you’re coming back to the project in 5 years after having done nothing and you want to be able to skip right to using it. When we build something ourselves, we often hold a bit of internal knowledge from the design process that never quite goes away, so it’s almost always a lot easier for us to reverse engineer something we’ve made, than it is for someone else with zero fore-knowledge to do it themselves.

    Generally this can be a bit of a nightmare, but if you minimize the user facing segment it’s not all that bad, because it’s usually pretty minimal, and what would otherwise be a handful of pages, turns into 10 or maybe 15.

    as for existing documentation, the i3wm user guide is really good, it’s pretty minimalist but it leaves you enough to be able to manage.











  • i don’t know if i really like that definition. Going by the definition of a laboratory, it doesn’t really make much sense. I mean sure they’re a sterile environment, but it’s incredibly unlikely that a lab is wiped clean and built from scratch, unless you get millions of dollars, and a lot of free time, i guess.

    A lab is merely a place to do work with regard to studying, learning, or improving something.

    People often refer to their “homelab” as an entire server rack, you want me to believe that people are willing to wheel out their entire server rack and discard the entire fucking thing? I doubt it. A homelab is just a collection of gear, (usually commercial networking gear) intended for providing an environment for you to mess around with things and learn about stuff.

    In some capacity a homelab has to be semi permanent, if not for anything other than actually testing reliability and functionality of services and hardware, for the actual services themselves, because a part of the lab, is the service itself.