By the end of this lesson you will be able to
- Describe what a person in IT support, networking and Linux administration does in a normal week.
- Match skills you have already learnt to the first needs of each pathway.
- Choose one beginner project for a pathway and say what finished looks like.
- Set realistic goals for the next three months.
You have come a long way: from switching a computer on to reading logs and thinking about security. The question now is where to go next. There is no single correct road, and you do not need to choose for life. This lesson looks at three closely related directions that build on what you already know: IT support, networking and Linux administration. For each one you will see what the work is like, what you already have, what is missing and a first project that proves your skill.
How to choose a direction
Choose by what you enjoy doing, not only by what is fashionable. After a small project in each area, ask yourself three questions. Did the time pass quickly? Did I want to find out more when I got stuck? Would I be happy doing this for a few hours every week? A yes to those matters more than any list of the best jobs. You can also change direction later: all three pathways here share the same foundations.
- Troubleshoot faults
- Reset and recover accounts
- Explain clearly
First project: a fix guide
- Addresses and routing
- Wi-Fi and firewalls
- Diagnose with tools
First project: a network map
- Terminal fluency
- Users and services
- Logs and backups
First project: a managed virtual machine
Read this figure as text
Three columns for IT support, networking and Linux administration with their focus and a typical first project.
Three columns. IT support: helping people with their devices, accounts and software; focus on troubleshooting and clear communication; first project is a personal fault log and fix guide. Networking: designing and fixing the links between devices; focus on addresses, routers and diagnosis; first project is a documented map of your home network. Linux administration: looking after Linux computers and servers; focus on the terminal, users, services and backups; first project is a virtual machine you set up, secure and back up.
IT support
IT support, often called a Help desk or service desk role, is the front line of technology. People ring or message when something does not work: they cannot sign in, the printer is silent, a file has vanished. Your job is to find out what is wrong, fix it or pass it on to the right person, and keep the person informed. Most work is recorded in a Ticket: a short written record of the problem, what was tried and the result. The best support staff are calm, patient and clear, and these soft skills matter as much as technical ones.
You already have the heart of it: the troubleshooting method, reading error messages, finding evidence, asking precise questions and recording solutions. What is usually missing is breadth (more hardware, more software, more operating system versions) and practice with real people. Those come with time and repetition.
- Skills to add: managing accounts and passwords safely, setting up printers and shared folders, basic remote support, writing short plain-language instructions.
- Beginner project: keep a personal fault log. Every time something goes wrong on your own or a friend's computer, write the symptom, the evidence, what you tried and what fixed it. After twenty entries, turn the best five into a one-page guide for a family member.
- Beginner goal: in three months, fix five real faults on your own and be able to explain each one in plain words.
Networking
Network technicians and engineers build and look after the links that join devices: cables, Wi-Fi, switches, routers and firewalls, and the rules about addresses and names that make them work. A normal task might be working out why one room has weak Wi-Fi, planning addresses for a new office or tracing why a website cannot be reached. You have already met the main ideas: IP addresses, DHCP, DNS, ports, packets and diagnostic tools such as ping and traceroute.
- Skills to add: subnetting (splitting a network into smaller ones), how routers share routes, VLANs (virtual separate networks on the same cables), reading network diagrams and, later, configuring real equipment.
- Beginner project: draw and document your home network. List every device, its IP address, how it connects and what it is for. Find the default gateway and the DNS server. Take a measured speed and signal check in three rooms and write what you would change. Keep the document up to date.
- Beginner goal: in three months, explain, without notes, what happens from typing a web address to seeing the page, and subnet a simple private network on paper.
- Step 1: List devices
- Step 2: Record addresses
- Step 3: Find gateway and DNS
- Step 4: Draw the map
- Step 5: Test and record
Read this figure as text
A flow of five steps from listing devices to reviewing the finished network map.
A flow of five steps. 1 List every device on the network. 2 Record each device's IP address and how it connects. 3 Find the default gateway and the DNS server. 4 Draw the map with a diagram. 5 Test one change and record what happened. The finished map is the proof of your skill.
Linux administration
A Linux administrator looks after computers that run Linux, very often servers with no screen that are reached through the terminal. The work is the module you have just finished: accounts and permissions, updates, services, logs, storage and backups, done carefully and repeatably. As the number of machines grows, administrators write scripts so that a task done once by hand can be done the same way every time.
- Skills to add: comfortable terminal use every day, a text editor in the terminal, installing and configuring a service, remote login with keys, scheduled jobs and writing safe scripts.
- Beginner project: create an Ubuntu virtual machine, set up a standard user and an administrator user, turn on automatic security updates, write down your backup plan and complete one restore drill. Finish by writing a one-page runbook, which is a set of instructions for a colleague who has to look after it.
- Beginner goal: in three months, spend twenty minutes a day in the terminal on your practice machine and finish the runbook.
- Learn one ideaSmall and specific
- Build with itOn a practice machine
- Write it downNotes and fixes
- Ask for feedbackA friend or forum
- ImproveThen pick the next idea
Read this figure as text
A cycle of five steps: learn a little, build something, write it down, ask for feedback, improve.
A cycle of five steps repeated again and again. 1 Learn one small idea. 2 Build something with it. 3 Write down what you did and what went wrong. 4 Ask a friend or a community for feedback. 5 Improve the project, then return to step 1 with the next idea. The centre says: repeat weekly.
Certificates, portfolios and honest expectations
A Certification is an exam-based qualification from a vendor or a standards body. Employers sometimes ask for them, particularly for support and networking roles, and a syllabus is a useful checklist of what to learn. Examples are CompTIA A+ for support, Cisco CCNA for networking and the Linux Professional Institute LPIC-1 or CompTIA Linux+ for Linux. The exams cost money, and the content changes, so check the current details on the organisers' websites before deciding.
A Portfolio is a small collection of evidence that you can do the work: your fault guide, your network map, your runbook. Employers and clients often trust a clear, honest portfolio more than a list of courses. Keep it free of private information such as real passwords and real addresses.
| Stage | Time | What you can usually show |
|---|---|---|
| Foundations (this academy) | Done | Troubleshooting method, files, networks, terminal, security basics |
| First project in one pathway | 1 to 3 months | A fault guide, network map or managed virtual machine |
| Study for a first certificate, if you choose one | 3 to 6 months | A certificate and a small portfolio |
| First paid or voluntary experience | Varies widely | Helping a school, a church or a small business with real faults |
Common mistakes
✖ Instead of: Collecting courses and certificates without building anything.
✔ Do this: Build a small project for every topic and keep it in a portfolio. Evidence of doing beats a list of courses.
✖ Instead of: Trying to learn all three directions at once.
✔ Do this: Choose one for three months. The shared foundations carry across if you change later.
✖ Instead of: Studying in rare long bursts.
✔ Do this: Short, regular sessions of 30 to 60 minutes beat one long session a month.
✖ Instead of: Practising on machines you do not own.
✔ Do this: Use a virtual machine or your own spare computer.
If something goes wrong
- I do not know where to start.
- Start with the taster practical. One hour in each direction gives real information about what you enjoy.
- I keep missing my study sessions.
- Reduce the plan to a small block you can always keep, such as 30 minutes on two fixed days, and link it to an existing habit.
- The terminal commands for the taster do not work on Windows.
- Use PowerShell and the Windows commands from the earlier lessons, for example
Get-Serviceinstead ofsystemctl. - I feel behind other people.
- Compare yourself with your own list from three months ago, not with others. Keep your fault log and project notes so that you can see your progress.
Key terms
- Help desk
- The team that people contact first when their technology does not work.
- Ticket
- A written record of one problem, what was tried and how it ended.
- Certification
- A qualification, usually from an exam, that shows you know a set of skills.
- Portfolio
- A small collection of your own work that shows what you can do.
- Shell script
- A text file of commands that the shell runs in order, so you can repeat a job with one command.
Practise it for real
Reading is not the same as being able to do it. Complete these on your own computer, then tick only what you have actually done. These ticks are your own honest record: nothing checks them for you.
Try a one-hour taster in each direction
Spend about an hour on each. For support, write a fault-log entry for a real problem you fixed recently. For networking, find your computer's IP address and default gateway and write them down with a sentence about what each does. For Linux, open a terminal and run uname -r, df -h / and systemctl --failed (on Windows, use the matching PowerShell commands from earlier lessons). Then rank the three by how much you enjoyed them and write one sentence saying why.
Challenge: write a three-month plan
Pick one direction and write a plan of one page. It needs a clear goal in one sentence, a beginner project and what finished looks like, how many hours you can really give each week, three milestones with dates and one way you will get feedback, such as asking a friend to follow your guide. Say what you will do if you miss a week.
Knowledge check
6 questions. You need 80% to pass. Mistakes here are part of learning, and you can retry as often as you like.
Summary
- IT support, networking and Linux administration share foundations you already have.
- Choose by enjoyment, using a small taster project in each.
- A project and portfolio prove skill, and certificates give structure.
- Set a three-month goal with weekly hours you can really keep.
- Practise only on machines you own, and ignore promises of quick jobs.
Checklist: can you do these?
Marking a lesson as read does not prove you can do it. Skills count as demonstrated when you pass the quiz (not yet) and complete the practical tasks (not yet).
Related lessons
References and further reading
Official sources for details that can change between versions.
- CompTIA A+ certification (CompTIA)
- Cisco Networking Academy (Cisco)
- Linux Professional Institute (Linux Professional Institute)
- Ubuntu tutorials (Canonical)