Engineering Focus

Three layers of the same control problem

Programmable networks, distributed software, and future-network experiments look different on the surface. I study them together because each asks how intent becomes state, how state is observed, and what happens when communication fails.

01 · Operate

Network Automation

Topology as data, configuration as intent, model-driven interfaces, and validation as a required step—not an afterthought.

Nokia SR Linux Containerlab Ansible YANG / gNMI

How I approach automation

02 · Coordinate

Go Distributed Systems

APIs, service boundaries, replication, secure communication, messaging, persistence, and observability for network-aware systems.

Go gRPC RabbitMQ PostgreSQL

Explore the systems track

03 · Rethink

Future Networks

NDN/ICN, Delay-Tolerant Networking, LEO/NTN emulation, and control-plane questions for moving or intermittently connected networks.

NDN / ICN DTN LEO / NTN NetSatBench

Explore the research direction

Shared Method

What stays constant across the three tracks

  1. Make the system rebuildableTopologies, dependencies, configurations, and run steps should be explicit.
  2. Separate intent from mechanismThe desired outcome should not disappear inside transport-specific commands.
  3. Treat failure as behaviorTimeouts, partitions, invalid state, and recovery paths belong in the design.
  4. Validate with evidenceLogs, queries, metrics, packet behavior, and test output make claims reviewable.
  5. Explain the boundaryFinished work, reproduced work, current learning, and future plans should remain distinguishable.

Evidence Map

Where each focus appears on this site

Focus Project evidence Knowledge evidence
Network automation SR Linux labs, CCNP labs Automation checklist
Go systems Tolerex, Inventory API, Netreka Nexus gRPC control-plane note
Future networks DTN labs, NDN labs, NetSatBench guide Research reading library