38 entries · filter: all
01 · signal ↗
Rahul on Instagram — photographs and observations beyond the network console.
Open this instagram signal in a new tab.
02 · signal ↗
Rahul on GitHub — network automation guides, labs, and experiments.
Open this other signal in a new tab.
03 · signal ↗
CMLv2 Simple Topology — build a repeatable Cisco Modeling Labs topology with Python.
Open this other signal in a new tab.
04 · play
Rahul is Spiderman
A fictional visual experiment: Rahul imagines the network engineer behind the mask.
05 · play
Rahul is Peter
A fictional visual experiment: Rahul steps into a playful comic alter ego.
06 · essay
A Network Engineer’s Roadmap to Automation
Automation is not a jump from the CLI to a platform. It is a sequence of safer, more observable habits.
07 · essay
MCP for Network Operations: Tools, Boundaries, and Trust
MCP can give an assistant useful network context, but the protocol does not make a tool safe by itself.
08 · essay
Hybrid Cloud Routing: When the Data Center Meets AWS
Hybrid routing becomes difficult when two independently sensible networks meet and their assumptions collide.
09 · essay
Terraform for Network Engineers: State, Review, and Change Discipline
Infrastructure as code changes the interface to the network, not the responsibility for the outcome.
10 · essay
Observability Before Automation
Automation without observability makes changes faster while making mistakes harder to explain.
11 · essay
Safer Firewall Policy Automation
Firewall automation must preserve intent, ownership, and an explainable path back to the request.
12 · essay
Building CMLv2 Labs with Python
A programmable lab turns network learning into a repeatable experiment instead of a fragile collection of screenshots.
13 · essay
Eleven Years in NetOps: Lessons That Still Hold
Platforms change quickly; the habits behind reliable network operations change much more slowly.
14 · journal
Why Network Engineers Should Learn DevOps Concepts
Version control, reviewable changes, testing, and observable delivery are not software-only ideas. They give network teams a shared language for reducing change risk.
15 · journal
Learning in Public
Publishing a small lab or an unfinished explanation creates a useful deadline: understand the idea well enough that another engineer can reproduce it.
16 · journal
What Makes Automation Safe
Safety comes from narrow scope, explicit inputs, previewable intent, approval where consequences are high, and proof of the resulting state.
17 · journal
Documentation Is Infrastructure
A rack elevation, route diagram, owner field, and rollback note carry operational traffic of their own: they move understanding between people and across time.
18 · journal
The Calm After a Clean Change
The best change window can feel uneventful. That calm was built earlier through research, prerequisites, evidence, and agreement about when to stop.
19 · journal
Observability and Humility
Telemetry is a reminder that our diagram is a hypothesis. The running system gets the final word, especially when it contradicts the plan.
20 · journal
Small Python Scripts Compound
An inventory check or certificate helper may look modest. Reused, reviewed, and improved, it becomes a building block for a safer operational system.
21 · journal
AI Agents and Earned Trust
An agent should begin by retrieving and explaining. Mutation comes later, behind narrow tools, approval, and independent verification.
22 · journal
Lab Before Production
A lab will not reproduce every production condition, but it is still the cheapest place to expose a wrong assumption about syntax, order, or behavior.
23 · journal
Pune, Global Systems, Packet by Packet
A career can be rooted in one city while touching backbone networks, global data centers, and clouds. The work still arrives one path and one careful change at a time.
24 · visual
A Packet’s Long Way Home
A visual note on the forward path, return path, and the stateful systems between them.
25 · visual
Where Hybrid Routes Meet
Transit, policy, and ownership at the border between a data center and AWS.
26 · visual
Inside a Change Window
The quiet sequence of pre-check, execution, observation, decision, and closeout.
27 · visual
Three Data Centers, One Operating Story
Mumbai, Frankfurt, and Munich connected by documentation and repeatable handover.
28 · visual
The Programmable Network Lab
A topology treated as disposable infrastructure and a durable experiment.
29 · visual
Certificate Renewal as a Pipeline
Import, install, associate, save, and verify—drawn as one bounded workflow.
30 · visual
Failure Domains Hide in Plain Sight
Two lines on a diagram can still share one provider, policy, or operational dependency.
31 · visual
Rack, Cable, Label, Repeat
Physical discipline as the first layer of remote operability.
32 · visual
The Automation Trust Ladder
From read-only inventory to proposed changes, reviewed execution, and verified state.
33 · visual
Pune to the Global Route Table
A visual field note about learning and operating across geography.
34 · signal ↗
Network Automation Beginners Guide — open-source starter path for network engineers.
Open this other signal in a new tab.
35 · signal ↗
Building CMLv2 topologies with Python — hands-on prep for AUTOCOR.
Open this linkedin signal in a new tab.
36 · signal ↗
Launching the “Figuring Out” series — Docker, Containerlab, and cross-functional NetOps concepts.
Open this linkedin signal in a new tab.
37 · signal ↗
Why network engineers should care about AWS DevOps Agent + Azure SRE Agent integration.
Open this linkedin signal in a new tab.
38 · signal ↗
Claude Code + MCP for network automation — experimenting with RAG for playbook execution.
Open this linkedin signal in a new tab.