BoredomBusted — Find Your Next Favorite Thing To Do
Discover hobbies, activities, places, and ideas that spark joy. Whether you're looking for something creative, active, social, or relaxing, BoredomBusted helps you find your next favorite thing to do.
Browse our hobby guides, things-to-do collections, and place ideas to never be bored again.
Most think system administration is just fixing tech issues — it's actually about building complex networks and troubleshooting through real-world scenarios.
Learning system administration as a beginner involves understanding the fundamentals of setting up, configuring, and maintaining computer systems, which can include servers, networks, or virtual machines in your home lab.
You're managing real infrastructure, not writing code.
Unlike programming or cybersecurity, the feedback is immediate: something either connects, boots, or it doesn't.
Engaging in system administration involves hands-on tasks like monitoring server performance, troubleshooting network issues, automating processes with scripts, configuring server software, and setting up virtual environments. You log into terminals, check system metrics, write scripts to streamline tasks, and iteratively build and test configurations, often using spare hardware or cloud instance…
System administration induces a flow state through deep engagement in problem-solving, offers immediate feedback with quantifiable results from scripts, and provides a sense of accomplishment as you create reliable systems, all while introducing novelty through constant technological evolution.
You think system administration is IT support. Fixing printers. Resetting passwords for people who can't remember them.
That assumption is costing you a genuinely interesting hobby.
The real work is closer to engineering than maintenance. You're writing automation scripts, managing networks, and making dozens of services talk to each other without falling over. Security, performance, and reliability are all design decisions — the choices a sysadmin makes determine whether a server handles 10 users or 10,000.
Here's what that looks like on a Tuesday night. You spin up a Linux virtual machine on your laptop and configure a web server from scratch. Then port 80 stops responding and you have no idea why.
Reading logs.
Forming a hypothesis.
Testing it.
That's the whole hobby — the broken thing isn't the obstacle, it's the point. You're not following steps anymore. You're doing the actual work.
The next question is what you need to run any of this — and the answer is probably already sitting on your desk.
Watching someone else manage servers looks like quiet competence – a few keystrokes, a clean terminal, everything just works. Your first session will feel nothing like that. The gap between "I understand what this does" and "I can do this without breaking something" is where most people stall.
Week one, you spend more time reading error messages than actually administering anything. That's not a detour – reading error messages is the whole job. Week two, you break a permission setting, panic, then realize you can recover it. The recovery is the real lesson, not the break.
Week three, something works on the first try and you immediately distrust it. Week four, you start recognizing patterns in errors instead of just reacting to them. That shift – from reacting to recognizing – is the only milestone that actually matters in month one.
Before your first session, set up a virtual machine and treat it as disposable – not a backup plan, your entire environment. Vagrant or VirtualBox gives you a sandbox you can destroy and rebuild in minutes. Without it, every mistake feels catastrophic. With it, every mistake is just data.
Ugly. Slow. Nothing looks like the YouTube video.
The terminal doesn't care about your confidence. It cares whether the command is right. People who get good at this are the ones who stop resisting that feedback loop and start using it. That loop – fast, honest, relentless – is the actual skill you're building. The next section covers the mistakes that keep beginners stuck in the painful half of it longer than necessary.
When to start: Early morning
Duration: 1-2 hours
Cost to try: $0
Success criteria: if you finished without errors in your VM setup, do session 2.
New sysadmins hit permission errors once and just sudo everything forever – it feels like solving the problem, but it's actually becoming the problem.
Switch to a non-root user immediately and use sudo only for specific commands, so you build the habit of knowing why you need elevated privileges, not just that you do.
When everything's working, logs feel like noise – so beginners ignore them until a crisis, then have no baseline to compare against.
Spend 10 minutes a week reading /var/log/syslog or journalctl on a quiet system, so you know what normal looks like before abnormal shows up.
There's no obvious harm until there is – and by then, you've learned an expensive lesson on someone else's (or your own) production machine.
Spin up a free-tier VM on AWS or a local VirtualBox instance, and break things there where the only consequence is a rebuild.
Beginners configure ufw or iptables once, think they're done, and never revisit it – so the ruleset quietly becomes a fossil that no longer matches the actual system.
Audit your firewall rules after every major software install by running ufw status verbose and asking whether each open port still needs to be open.
The internet gives you copy-pasteable answers fast, which means you run flags you don't understand on systems you're responsible for.
Before running any unfamiliar command, pull up man [command] and read just the OPTIONS section – it takes three minutes and immediately separates you from 80% of beginners.
System administration is practiced wherever you have a computer — your home desk, a spare laptop, or a rented cloud server that costs less than a coffee per month. Most of the real learning happens in purpose-built virtual environments, not physical venues.
The r/sysadmin subreddit and the Spiceworks Community are the fastest starting points. Both have active forums where you can ask location-specific questions and find local professionals.
LOPSA (League of Professional System Administrators) is the closest thing to a national governing body. Their local chapters host events and connect working sysadmins with people just starting out.
When you show up or post for the first time, say: "I'm setting up a home lab and want to break things on purpose — where do I start?" That framing signals you're serious, not just browsing. It usually gets you a pinned resource list, a lab architecture suggestion, and someone offering to walk you through your first build.
Instead of managing physical hardware, you manage virtual infrastructure through a browser or CLI.
This is where most new sysadmin roles are heading – and where the job market is thickest right now.
Best for anyone starting fresh who doesn't have a server room to play in.
Free tiers on AWS and GCP get you surprisingly far before you spend a dollar.
The classic. Command line, configuration files, no hand-holding.
It's the foundation most other variants assume you already have – skip this and you'll feel it later.
Best for people who want to understand how systems actually work, not just click through dashboards.
Active Directory, Group Policy, and a lot of enterprise environments still running Windows infrastructure.
Less glamorous than cloud work, but incredibly common in mid-sized companies that aren't migrating anytime soon.
Best for people targeting corporate IT roles over startup or DevOps tracks.
This is sysadmin work pushed into software development pipelines – automation, CI/CD, infrastructure as code.
It's not a beginner variant. You need solid fundamentals first, or the tooling becomes noise.
Best for sysadmins who've got a year of experience and want to move toward higher-paying engineering roles.
Running your own servers at home – old hardware, virtual machines, self-hosted services.
No stakes, no boss, no production outage at 2am. It's the best sandbox you can build for learning.
Best for complete beginners. Start here if you have zero access to real infrastructure.
Readers who enjoy this often gravitate toward Nonfiction Reading next.
Most beginners optimize for memorizing commands. That's not the job – reading system behavior is.
The one skill is log correlation: the ability to look at output from multiple sources – syslog, auth logs, application logs, resource monitors – and reconstruct what actually happened and in what order.
Not just reading one log file. Connecting threads across all of them.
Without it, you're guessing – rebooting services, applying patches blind, hoping the problem disappears. When you can correlate logs, every incident becomes a story with a beginning, a cause, and a fix you can actually explain to someone else.
Systems stop feeling chaotic. They start feeling like things that tell you what they need.
Most people who try sysadmin either get quietly hooked within a month, or realize they were drawn to the idea of it rather than the actual work. Eight sessions over 30 days — roughly two per week — is enough time to find out which one you are.
The first few sessions feel like reading a foreign language. By sessions five or six, patterns start emerging — and whether that moment of recognition arrives is the real test.
If you keep opening the terminal even when nothing's broken, that's not habit — that's the hobby taking hold. Poking around logs out of curiosity, or spinning up a second VM just to see what happens, means you're ready to go deeper. Pick a direction: networking, security hardening, or cloud infrastructure.
If you finished all eight sessions but felt nothing either way, the exercises may have been the wrong frame, not the wrong hobby. Extend by four sessions, but drop the tutorials and solve a real problem — set up a home media server, or host something you'd actually use.
If you dreaded sitting down every time, take that seriously as data. The daily reality of sysadmin is ambiguous error messages, broken dependencies, and troubleshooting that takes hours to produce a one-line fix. If that loop produced no payoff feeling across eight sessions, the fit isn't there — and that's a clean answer.
Sysadmin problems don't resolve on a schedule. A config issue can consume two hours without warning, and stopping mid-troubleshoot is genuinely painful. If your life can't absorb unpredictable time blocks, this becomes a stressor, not an outlet.
A perfectly running system is invisible by design. If you need fast, visible creative output to stay motivated, the reward structure here — mostly the absence of problems — will grind you down.
If hardware access or a stable home network is a genuine constraint — not a preference, an actual limit — cloud-based labs like AWS Free Tier or DigitalOcean exist as workarounds. But they add friction that compounds for beginners and can quietly kill momentum before the hook sets.
You're lying in bed replaying why a service failed — and you're not annoyed, you're curious. If you've ever rage-Googled a network error at midnight and felt more alive than frustrated, that pull doesn't go away — it gets louder.
Still looking for something to do? Browse things to do when bored for more ideas.
You should have a basic understanding of how computers and networks work, but formal IT training isn't required—most people start with beginner knowledge of operating systems like Windows or Linux. Strong problem-solving skills, patience, and curiosity about how systems function are more important than advanced technical background.
Basic competency typically takes 6–12 months of consistent study and hands-on practice, while advanced proficiency requires 2–3 years of experience managing real systems. The timeline varies based on how much time you dedicate and whether you're learning on the job.
No—you can practice with free tools like Linux distributions, virtual machines, and open-source software that professionals use in real environments. Many learning resources are also completely free, making system administration one of the more accessible hobbies to start.
It has a learning curve, but it's not inherently difficult if you approach it systematically and practice on safe test systems first. Breaking tasks into smaller steps and learning one concept at a time makes it manageable and even enjoyable for most people.
You can manage your home lab, optimize your personal network, secure your devices, help friends and family with tech problems, or set up servers for gaming, file sharing, or web projects. Many hobbyists use it as a stepping stone to IT careers or simply for the satisfaction of mastering their digital environment.
Even 5–10 hours per week of focused learning and hands-on practice can build real skills, though 15–20 hours weekly accelerates progress significantly. Consistency matters more than cramming—regular practice helps concepts stick and builds the troubleshooting intuition that experts develop.