Welcome. Let’s all settle in, shall we?
An introductory article on what to expect here
Hey, Marshud here👋🏼.
I have been a backend guy for some time now, dealing with APIs, queues, databases, and the usual grind that keeps systems running. Now I’m on a deliberate mission to level up my entire stack starting with foundation technologies that many people skip, then build all the way up to production-grade machine learning.
This blog is my live journal of that journey.
No polished courses, no fake expert vibes, just me figuring it out step by step, sharing some notes, dumb mistakes, and the “Hmm, that actually worked” moments when they happen.
What You’ll See Here
I am tackling this in a very intentional order:
Cloud Networking:
I realised most cloud problems like latency, costs, outages, security etc, trace back to networking. So I’m going hard on VPCs, peering, load balancers, firewalls, private service access, hybrid connectivity, and all the invisible plumbing that makes or breaks production cloud environments. Expect lots of “why is this taking so long?” Posts, terraform configs that finally fixed my egress bills, and stories from when I accidentally open-sourced my entire subnet (no, it won’t happen😂).
Cloud Computing:
Once networking feels rock-solid, I’ll move into the broader cloud picture. I’ll take on the real horror stories of IAM, observability, cost optimisation, serverless vs GKE vs VMs, disaster recovery, and how to actually design systems that don’t explode at 3 a.m. This is where I’ll start connecting the dots between backend habits and cloud-native thinking.
AI/ML and MLOps:
After I’m confident in the infrastructure, I will go all-in on machine learning and MLOps. I want to build production-ready pipelines on Vertex AI, Kubeflow, feature stores, model monitoring, and everything that makes AI actually shippable and not just Jupyter notebooks. By the time I get there, I’ll have the networking and cloud foundation to understand why things break in production, not just how to train a model.
What to expect along the way
Spontaneous updates: I’ll post when I learn something, not when the calendar says so.
First-person battle stories: If I run into something and I find it interesting after solving it, I am definitely sharing that one.
Code, configs, and commands: Copy-paste ready snippets with explanations of what I tried and failed before.
Zero fluff: I have no intention of selling courses, and I’m not pretending to have all the answers. I am just documenting my past so you can skip the same pain.
Why I’m sharing this publicly
Writing forces me to understand the material.
If my mistakes and breakthroughs can save even one person the same late-night Google rabbit holes, it’s worth it
I want to look back in a year and see how far I’ve come
How to follow the Journey
New posts will drop whenever something worth sharing happens (no fixed schedule).
I’ll cross-post or share summaries on LinkedIn, X, dev.to, or Reddit
If you want to ride along, subscribe here, on X or LinkedIn so you can know as soon as I drop something
Now that this is known, let me get cooking. See you in the next one
