06-07, 11:00–11:50 (EST5EDT), AlmaLinux (BallroomC)
The difference between a company project and a homelab project is the company project gets a team to support it when it becomes sewage. So let's talk about preserving your time when you can't hire a team for your house IT.
We all know that our time is limited. If our tasks require deep contextual thinking, such as maintaining services, we could find ourselves pulled away by too many commitments we'd previously made. You've probably said this before: "We need to tear it down and build it again the right way." If you were speaking of your past commitments, what exactly went wrong between the past and today? Why are yesterday's decisions hurting you today?
In a home context, the "hurt" manifests as "Now it's broken and one day I'll fix it." This is why we can't have nice things for more than a year or two. So -- what are some strategies we can use to keep our nice things?
In Short:
- Separate "Home Dev" and "Home Prod"
- Nothing goes manually into "Home Prod", only via automation.