Linux Beyond the Classroom: What IT Support Is Teaching Me

Learning Linux through courses is one thing.

Using it when you actually need to understand why something isn't working is completely different.

I'm Mateo Benjamín Italiano, a Systems Engineering and Cyber Defense student from Argentina. I also work in IT Support, where I've been getting more hands-on experience with Linux and troubleshooting.

One of the biggest things I'm learning is that knowing commands isn't enough.

Commands are not the goal

When I started learning Linux, it was easy to think about it as a collection of commands:

ls
cd
pwd
ip
ping
grep
systemctl

Learning what they do is useful.

But real troubleshooting requires something else: understanding why you're running them.

Instead of asking:

"Which command should I use?"

I'm learning to ask:

"What am I trying to verify?"

That small change makes a huge difference.

Troubleshooting is a process

A problem that looks complicated becomes much easier when you break it down.

For example:

Something isn't working
↓
What exactly is failing?
↓
Can I reproduce the problem?
↓
What information can I collect?
↓
What changed?
↓
Test a hypothesis
↓
Verify the solution

The command comes after the question.

Linux is also teaching me networking

Working with Linux has also made concepts like IP addresses, interfaces, DNS, routes, services and ports much more tangible.

Things that can feel abstract while studying become easier to understand when you actually have to troubleshoot them.

And this is one of the reasons I'm increasingly interested in cybersecurity as well.

Before analyzing attacks, logs or suspicious network activity, having solid fundamentals in operating systems and networking matters.

Breaking things is part of learning

I also started using Linux in my own learning environment so I can experiment without being afraid of making mistakes.

Install something.

Configure it.

Break it.

Figure out why it broke.

Fix it.

Document what happened.

For me, that cycle has been much more valuable than simply memorizing commands.

What I'm focusing on now

I'm still learning, but my current goal is to strengthen the fundamentals:

Linux
Networking
Troubleshooting
System administration
Cybersecurity fundamentals

I'll be using DEV to document some of the things I learn along the way — especially when a concept finally goes from "I studied this" to "now I understand why this works."

If you're learning Linux too, what concept took you the longest to really understand?

Thanks for reading! 👋

— Mateo Benjamín Italiano