Why We Started a YouTube Channel - And What We're Trying to Build

There's a particular kind of frustration that comes from watching someone learn IT the wrong way.

I've seen it dozens of times. A motivated beginner sits down with a course they paid too much for, follows along with a tutorial that was outdated the day it was published, and emerges three weeks later technically able to recite definitions but unable to actually do the thing the course was supposedly about. They can tell you what a container is. They can't deploy one. They know the OSI model by heart. They've never once read a real network log.

This is not their fault. It's the fault of how IT education has been packaged for the last decade — as content rather than as craft.

Today, we're announcing something we hope will be a small correction to that pattern. Dargslan is now on YouTube, and the channel exists for one specific reason: to teach IT skills the way they should have been taught all along.

You can find us here: youtube.com/@Dargslan

The Story So Far

For those who haven't come across our work before, Dargslan started as a quiet project — a small library of eBooks and free guides covering Linux, DevOps, and Cybersecurity. The original idea was modest. There were a lot of people trying to break into IT, or move sideways within it, who couldn't afford the boot camps and didn't trust the certifications. They needed material that was honest about what these jobs actually involve, written by someone who'd done them rather than someone who'd merely studied them.

Over time, that small project grew. Readers started writing in with questions, suggestions, requests for topics we hadn't covered. A community formed around the work — not loud, not viral, but real. People who actually wanted to learn, and who treated us like a trustworthy resource rather than another piece of internet noise.

That trust is something we take seriously. It's also the reason this YouTube channel took longer to launch than it probably should have. We didn't want to do it badly. We didn't want to add to the pile of fast, shallow tech content already crowding the platform. If we were going to be there, we wanted to be there for a reason.

Why Video, Why Now

There's an honest answer to this question, and it's that some things genuinely cannot be taught in writing.

You can describe, in careful prose, how to debug a failing systemd service. You can lay out the commands, the expected outputs, the common pitfalls. And someone reading that will probably understand it well enough to repeat it. But they will not understand it the way someone who has watched the process unfold understands it. They will not see the hesitation when a command returns something unexpected, the moment of recognition when the journal log reveals the actual problem, the small tactical decisions about which thread to pull on first.

Video shows you how someone thinks through a problem. That is, in many cases, the entire skill. The commands themselves are public information — you can find them in any man page. What's rare is seeing how an experienced person sequences them, which ones they reach for first, what they do when something doesn't work the way they expected.

This is what we want the channel to be. Not just instructional content. A window into how the work actually feels.

What You'll Find There

The early focus will mirror what we've always done in writing: Linux, DevOps, and Cybersecurity, with occasional excursions into adjacent topics when they earn the detour.

Concretely, you can expect a few different formats:

Walkthrough tutorials — start to finish, real problem to working solution. These will run longer than the YouTube algorithm probably wants them to, because real problems take real time to solve. We'd rather lose impatient viewers than fake-shorten something that needs space to breathe.

Concept deep-dives — for the topics that get glossed over everywhere else. SELinux. systemd internals. The actual mechanics of how TLS handshakes work. Things people pretend to understand on resumes but rarely sit down and study properly.

Real-world breakdowns — taking actual incidents, configurations, or scenarios and unpacking them. What went wrong in this outage. Why this architecture is fragile. What a security audit actually looks for when it walks through a server.

Beginner foundations — because the audience that asks us the most questions is the one just starting out, and they deserve material that meets them where they are without talking down to them.

We won't be doing reaction videos. We won't be reviewing the latest framework that will be irrelevant in eighteen months. We won't be racing to upload the same news every other tech channel uploaded six hours ago. There's no shortage of that content already, and we'd be bad at it anyway.

The State of Tech Education

It's worth saying something about why this matters, because it's easy to dismiss "we started a YouTube channel" as just another small announcement in a sea of small announcements.

Tech education is, broadly speaking, in a strange place right now. The amount of available material has exploded. The quality has not kept pace. There are more courses, more tutorials, more articles, more videos than ever before — and somehow the average person trying to learn IT seems to have a harder time than they did ten years ago.

Part of the reason is that AI has flooded the lower tiers of educational content with material that is technically coherent but pedagogically empty. Articles that explain what something is without ever explaining why it matters. Tutorials that walk through the happy path and never address what happens when something goes wrong — which, in IT, is most of the time.

Part of the reason is that the incentives of the platforms reward the wrong things. Short videos get more views than long ones, even when the topic genuinely needs the time. Provocative thumbnails outperform honest ones. Content optimized for retention often sacrifices the parts that would actually teach you something.

We don't have a solution to all of this. But we can, in our own small corner, try to do it differently. Make videos that are as long as they need to be. Use thumbnails that describe what's actually in the video. Cover topics because they matter, not because they trend. Be the channel that someone watches at the end of a long workday and feels slightly smarter afterward rather than slightly more agitated.

That's the bar. We won't always clear it. But we'll keep aiming at it.

An Invitation

If you've read this far, you're probably the kind of person we made this channel for.

Come watch a video. Subscribe if you find it useful. Leave a comment if there's a topic you wish someone would cover properly. The channel will grow in the direction the community pushes it, and we want that community to be made of people who care about doing things well — not because it's profitable, not because it's trendy, but because the craft is worth caring about.

You can find us at youtube.com/@Dargslan.

For the eBooks, free guides, and everything else we've been building over the past few years, dargslan.com is still home.

Thank you for being part of this so far. The next chapter starts now.