A note from Suraj · Author of SRJahir Tech

Where to begin —
and why it matters.

I’m Suraj. I started this site because I was tired of tech tutorials that either dumb things down so much they teach you nothing, or pile on jargon to sound smart. So I wrote what I wish I’d had when I was learning.

— Suraj Ahir, working engineer · Cloud / DevOps

Most tech sites are just feeds — you read one post, drift away, learn nothing in particular. Here, you pick a track. Each track is a structured series. Each part builds on the one before. By Part 12, you actually get the topic — not just know the keywords.

Read at your own pace. One part a day, three a week, doesn’t matter. What matters is that you finish a track before jumping to the next.

Where are you right now?

Pick the row that sounds like you — I’ll send you to the right starting article.

The four tracks

Pick one. Finish it before starting another. That’s the whole rule.

Why this site exists

Four things I promised myself when I started SRJahir Tech.

One person, no ghostwriters

I write every article myself. No AI-generated filler, no outsourced bloggers. If a sentence feels off, that’s on me — and I’d rather you tell me than read something hollow.

A course, not a feed

Most tech blogs are infinite scroll. I built this as tracks instead, so the time you spend here actually compounds. Part 1 prepares you for Part 12. That’s the point.

If it’s not in production, it’s not here

I cut a lot of “you should theoretically know this” content. If a concept doesn’t show up in real engineering work, it didn’t make it into the article.

Free, no email gate

No paywalls, no “subscribe to read more”, no signup walls. Ads and the free tools at tools.srjahir.in pay the bills. You don’t.

Honest answers to common questions

Where should a complete beginner start?

If you’re totally new to tech, start with the Linux series. It’s the foundation every other track assumes you already know. If you’re not technical and want to understand markets, start with How Global Markets Work instead. Both paths assume zero prior knowledge — I built them for the version of me that didn’t know anything either.

How long does each track take?

Reading only, about two weeks if you do one part a day. Actually applying it — building things, breaking things, fixing them — takes 4 to 8 weeks. Don’t rush. The understanding compounds in the practice, not in the speed-reading. I learned that the hard way myself.

Do I need to follow the tracks in order?

Within a series, yes — Part 5 assumes you read Parts 1–4. Across tracks, no, except for one rule: Linux is the prerequisite for both DevOps and Cloud. If you skip Linux, those tracks will feel harder than they should. Save yourself the pain.

Is it really free?

Yes. All 100+ articles are free, forever. The site is supported by ads and the free PDF tools at tools.srjahir.in. There is no premium tier. There is no “upgrade to read more”. There never will be.

What if I get stuck?

Every article ends with key takeaways and a next-up link so you don’t lose momentum. For specific questions, try CloudAI — I built it specifically to explain technical concepts in plain language without the textbook tone.

Who actually writes this site?

Just me — Suraj Ahir. I’m a working engineer in cloud and DevOps. Everything you read here comes from things I’ve personally built, broken, or had to debug at 2 AM. That’s the only reason I think it’s worth your time. More on the About page.

If you stick with one track for two weeks, I promise you’ll learn more than you would from a year of random YouTube videos. Not because I’m a better teacher — but because structure beats consumption, every time.

See you in the first article.

— Suraj