AboutAwardsProjectsStackStatsActivityThinkingServicesContactBlog

Ganesh Angadi | DevOps Engineer Portfolio | Systems & Infrastructure

🚨 New Series: DevOps Duels drops every Sunday & Thursday! Check it out!

$ whoami — DevOps Engineer & Systems Engineering

I QUESTION
FRAGILE
ARCHITECTURE


$ man ganesh

System Thinker

Ganesh Angadi - DevOps Engineer Portfolio

Hi, I'm

GANESH ANGADI

[ STATUS: OPEN TO OPPORTUNITIES ]

Welcome to my DevOps portfolio. I don't build features; I design observable systems that fail gracefully. Focused on Linux internals, Kubernetes orchestration, and declarative infrastructure automation.

📍 Mysuru, Karnataka, India

Follow me on :

$ history | grep "milestones"

Recognition & Experience

1ST PLACEOpen Innovation · April 2026

MCP-Based Systems Engineering Hackathon

Built an MCP wrapper around an ISL translator — enabling AI assistant integration. Focused on the integration layer, not reinventing the tool.

24h · MCP track
MCPPythonAI IntegrationProtocol Design
INTERNSHIPArtsy Technologies Pvt Ltd · May 2026

AI & Machine Learning Intern

Selected for an AI/ML internship. Working on real projects alongside experienced professionals. Offer ID: OL-2026-VP9K07.

Verified · May 2026 - present
AI/MLPythonArtsy Technologies

$ ls -lh /opt/projects

Things I've Built

Currently Building

Things I'm Building

Building a centralized observability and recovery layer for software deployments. Open source, graph-native deployment tracking with root cause analysis and automated rollbacks.

🚀 Looking for open-source developers to collaborate! If you're interested in system architecture, graphs, or DevOps tools, I'd love to build this together.

[GitHub / Contribute] →

$ capabilities --depth=system-level

Systems Depth & Stack

Linux & OS Internals

$ ls -lh /proc/sys/kernel

├──File System
├──systemd Services
├──Linux Networking Stack
├──Bash/Shell Scripting
└──Permissions, Users & Groups

Containerization (Docker)

$ docker inspect --format='{{json .Config}}'

├──Docker Images & Container Lifecycle
├──Bridge & Host Networking
├──Volumes & Bind Mounts
├──Docker Compose Orchestration
└──Dockerfile Writing & Build Basics

Infrastructure as Code

$ terraform plan -out=tfplan

├──AWS Resources Provisioning
├──Variables, Inputs & Outputs
├──Terraform State Files
├──Modular Project Structure
└──Commands (Init, Plan, Apply)

Container Orchestration

$ kubectl get pods -n production

├──Pods & Core Workloads
├──Service Discovery & ClusterIP
├──Deployments & Scaling
├──Ingress Routing Basics
└──ConfigMaps & Secrets

$ tail -f /var/log/github/metrics.log

GitHub Contributions & Stats

github_metrics.log
$cat github_metrics.log
GitHub StatsTop Languages
$render-3d-contrib --theme=gitblock --animate
3D Contribution Graph

$ cat /var/log/latest_entries

Recent Articles

Public vs Private IPs: How NAT Quietly Keeps the Internet Alive

DevOps Duels8 min read

IPv4 vs. IPv6: The Internet's Biggest Fix is Still Unfinished

DevOps Duels3 min read

PostgreSQL vs. MongoDB: Relational vs. Document Databases

DevOps Duels8 min read
$ cd /blog→

$ cat /etc/sysctl.conf

I don't just build features.
I design systems.

Six principles I actually follow. Hover each one to see where it came from.

Think in control flow

Map the execution path. Understand what happens when, and why.

When I debug, I don't guess. I trace. Every system has a path — find it, follow it, understand where it breaks.

Model failure states

Design for what breaks, not what works. Every system has a failure mode.

A cron job silently failed for 11 days. No alerts. Just absence of signal. Now I design for failure first — happy path second.

Design for observability

If you can't measure it, you can't debug it. Logs, metrics, traces.

Before I ship anything, I ask: how will I know when this breaks? If I can't answer that, it's not ready.

Prefer explicit over magical abstractions

Magic is technical debt. Explicit is maintainable.

Every abstraction hides complexity. I prefer code that tells you exactly what it does — even if it's more verbose.

Break systems to understand them

Chaos engineering isn't optional. It's how you learn.

I deliberately kill services and simulate failures in dev. I need to know what happens before production finds out first.

A deploy without a rollback is a gamble

Every deployment needs a tested escape route.

3 hours of downtime. No rollback plan. No tested restore path. Rollback is now designed before deployment — not after.

$ systemctl list-units --type=service

How I solve
systems problems

Available for freelance. Hover each card to see how I actually think about the work.

01

Full Stack Development

End-to-end web applications — from schema design to deployed product.

"Schema is architecture. I design the database before writing frontend. Get it wrong early and you pay forever."

Next.jsReactNode.jsPostgreSQLSupabase
02

Android App Development

Cross-platform mobile apps using React Native. Offline-first by default.

"Networks are unreliable. I design for offline behavior from day one — not as an afterthought."

React NativeExpoOffline-firstREST APIs
03

DevOps & CI/CD

Deployment reliability, observability pipelines, fault-tolerant workflows.

"A deploy without a rollback plan is a gamble. I build pipelines that fail loudly and recover gracefully."

DockerCI/CDJenkinsGitLab CIBash
04

Infrastructure & Architecture

Systems designed to survive failure. Tradeoffs made explicit, not hidden.

"I ask the uncomfortable questions before you build — not after you're paged at midnight."

LinuxSystem DesignKubernetesMonitoringCloud
Let's work together →ganeshangadi13012006@gmail.com

$ ping -c 4 ganesh.online

Reach out

elsewhere

What I believe

Infrastructure is not magic — it is decisions with trade-offs. I make those decisions explicit.

I'm still learning. Still breaking things on purpose to understand them. Still questioning every abstraction I reach for.

If you're building something that needs to be reliable, observable, and honest about its failure modes — let's talk.

— Ganesh Angadi

DevOps Engineer · System Thinker · Mysuru, India