← Back to list

I Thought I Knew Linux… Until DevNet Made Me Realize I Didn’t

After my first experience with DevNet, I thought I had a decent grip on things.

Biplove Yadav · 2026-06-22 19:20 · 0 claps · 2.0 min read
#devnet #linux #networking #cisco-devnet #networking-tips
Open on Medium ↗
Wiki topics: 🔓 · Open Source

I Thought I Knew Linux… Until DevNet Made Me Realize I Didn’t

After my first experience with DevNet, I thought I had a decent grip on things.

Networking basics? Fine. Python basics? Kind of fine. Linux? “Yeah, I use commands sometimes… I’m good.”

Then Module 1 happened.

And it quietly exposed something I didn’t expect: I didn’t really understand Linux. I just used it.

The Illusion of Knowing Linux

Before this, Linux felt simple:

  • ls to list files
  • cd to move around
  • cat to read files
  • mv to rename things

It felt like enough.

But DevNet doesn’t just ask you to “use Linux.”

It expects you to think in Linux.

That’s a completely different thing.

The Lab That Changed the Way I Look at Commands

The Linux review lab wasn’t hard in a dramatic way. It was simple commands, file navigation, regex, system tasks.

But the pattern was clear:

You’re not being tested on memorization. You’re being tested on how quickly you can figure things out.

That’s where I started noticing gaps.

For example:

● I knew ls, but not why ls -l gives structured system insight.

● I knew grep, but not how powerful pattern matching actually is (like finding exactly what you need with grep '^taylor').

● I used sudo, but didn’t fully think about the permission layers in a system.

Small things. But they add up.

Then Python Entered the Picture

Right after Linux, Python showed up again.

Not advanced Python. Just the basics:

Lists. Loops. Dictionaries. Conditions. Simple logic.

At first, it felt almost too easy.

Until I realized the goal wasn’t just learning Python syntax.

It was this: Can you use Python to control systems instead of manually doing everything?

The Real Shift Happening in DevNet

The biggest change isn’t technical.

It’s mental.

Before: “What command do I run?”

After: “Why am I doing this manually at all?”

That question changes how you approach everything.

Because once you see the potential for automation, manual work starts feeling temporary.

What This Module Actually Trains You For

This part of DevNet isn’t about Linux or Python separately.

It’s about this combination:

Linux → control the environment ● Python → control the logic ● APIs → control real systems (which comes next)

It’s like slowly learning how to talk to machines properly instead of just operating them.

That’s the direction everything is heading in networking.

Final Thought

The strange part is how normal it feels while you’re doing it.

You don’t feel like you’re “transforming your skillset.” You just feel like you’re doing labs, running commands, and fixing errors.

But then one day you realize: You’re not just learning tools anymore. You’re learning how systems actually behave. And that changes how you see everything in tech.

Tags:

DevNet #Linux #Python #LearningJourney #Automation #Networking #Tech


메타데이터
post_id
d8d8ea582b0e
slug
i-thought-i-knew-linux-until-devnet-made-me-realize-i-didnt-d8d8ea582b0e
url
https://medium.com/@biplove.y/i-thought-i-knew-linux-until-devnet-made-me-realize-i-didnt-d8d8ea582b0e
canonical_url
https://medium.com/@biplove.y/i-thought-i-knew-linux-until-devnet-made-me-realize-i-didnt-d8d8ea582b0e
author_url
https://medium.com/@biplove.y
status
ok
fetched_at
2026-07-09 09:18:05