Why This Blog Exists, Day One
The first post on this blog, why I started, what tech I used, and why identity and access management felt like the right direction.
I’ve been a developer for years.
Not a great one. But good enough to be dangerous.
I built full-stack apps, APIs, backends, databases. The whole circus. I could spin up a MERN stack in my sleep. I could debug a broken API like it owed me money.
And then one day, I stopped and thought:
“Who’s actually securing all of this?”
That question wouldn’t leave me alone.
The Realization
The more I understood how systems work, how data moves, how identities are managed, how networks communicate, the more one thing became painfully clear:
The gaps are everywhere. And most people building systems aren’t thinking about them.
Not because they’re careless. Because they’re focused on shipping features, meeting deadlines, making things work. Security is an afterthought until it’s not, and access is usually the part nobody’s watching.
I didn’t want to be part of that problem anymore.
Why I Started This Blog
This blog isn’t a content strategy. It’s not a personal brand play. It’s not a “5 things you didn’t know about Linux” listicle machine.
It’s me, documenting what I’m actually learning, in the way I actually think.
Honestly. Technically. Without the fluff.
No AI slop. No recycled Stack Overflow answers dressed up as insights. Just real learning, written by a human who actually gives a damn.
I want to look back at this post after 10, 20, 30 years and say:
“That’s where it all started. That’s where I decided to go deep.”
The Tech Stack
I built this blog using:
- Jekyll, static site generator, simple and fast
- Chirpy Theme, clean, dark, minimal, perfect for technical writing
- GitHub Pages, free hosting, version controlled, zero maintenance
- Markdown, because I write better when I’m not fighting a WYSIWYG editor
Why this stack?
I wanted something that gets out of my way. No WordPress bloat. No Medium paywalls. No distraction.
Just me, a text editor, and the things I’m learning.
Why This Feels Right
I’ve been a developer for years. It taught me a lot, how systems are built, how they fail, how they scale.
But identity and access management? That’s where my head is now. Who has access, why they have it, and whether it still makes sense. SailPoint, Linux, networking, all the infrastructure underneath it, the stuff that actually decides whether a system holds up or falls apart.
It feels like I found what I was looking for.
Not because it’s trendy. Not because the salaries are good (though that doesn’t hurt). Because the problems are complex, meaningful, and never stop evolving.
That’s the kind of work I want to spend my career on.
What’s Coming
I’ll be writing about:
- Identity Security & SailPoint ISC, hands-on, real implementation
- Linux & Networking, deep, not surface level
- Core identity and security concepts, explained like you have a brain
- Tools, how they actually work, not just how to install them
- My raw learning journey, wins, failures, and everything in between
Some posts will be long and technical. Some will be short and direct. All of it will be real.
This Is Day One
I’m not an expert. I’m not pretending to be one.
I’m someone who decided to go deep on identity and access management, and document the entire thing honestly.
If that sounds like something worth following, stick around.
The first real posts are coming soon.
📧 hello.sahilahmad@gmail.com
🐙 github.com/sahilahmadofficial
💼 linkedin.com/in/sahilahmadofficial
— Sahil
Day One. September 2025.