Electronic Engineer and Network Architect specializing in routing, WAN, telematics, and automation.
Builder of practical tools for network architecture, terminal workflows, and infrastructure reliability.

I design network architectures where routing, WAN, Unix systems, and automation meet. My work is about turning complex requirements, device output, and day-to-day network signals into something clear enough to reason about, document, test, and improve.

Routing protocols are where networking gets interesting, and BGP is the part I enjoy most: BGP everywhere, but with deliberate policy, useful visibility, resilient WAN design, and architecture that can be explained when it matters.

I care about architectural clarity: understanding the path, knowing why traffic behaves the way it does, and leaving networks easier to operate, troubleshoot, and evolve than I found them.

route preference:
  bgp: everywhere
  policy: explicit
  wan: resilient by design
  tools: boring enough to trust

Fast terminal output highlighting for network devices and Unix systems, built to make dense CLI output easier to scan during real network engineering work.

• Dynamic profiles for network-focused terminal sessions.
• User-facing documentation at prismtty.com.
• Repeatable installs through Homebrew and Cargo.

brew install inxbit/tap/prismtty

Colored, concurrent ICMP/TCP ping monitoring for the terminal, built for quick reachability checks and cleaner visual feedback when watching multiple targets.

• Parallel host checks with terminal-friendly color output.
• ICMP and TCP modes for practical network validation.
• Lightweight workflow for troubleshooting paths, reachability, and service availability.

brew install inxbit/tap/pinghue

• WAN architecture, routing design, BGP, and route-policy clarity.
• Network automation for architecture validation and engineering workflows.
• Multi-vendor environments across Juniper, Cisco, VeloCloud, Fortinet, and the platforms real networks accumulate over time.
• Terminal UX, PTY behavior, parsing, and output highlighting.
• Release packaging, documentation, and project polish.

• Make the path visible before making it clever.
• Be the network janitor when needed: clean up stale assumptions, unclear policy, weak visibility, and designs that nobody can explain.
• Build small tools that solve real network engineering problems.
• Prefer safe defaults, clear documentation, and reproducible workflows.
• Keep automation readable enough to trust during changes and incidents.
• Treat polish as part of reliability, not decoration.

Portfolio · PrismTTY · GitHub