👋 Oh, hi! You found my corner of the internet.

I’m Satyajit Roy, but you can call me Roy. (It saves syllables for more important things, like variable naming debates).

I am a Technologist, Problem-Solver, and Chief Automation Officer of my own life. My philosophy is simple: “If I have to do it twice, I’m writing a script. If I have to do it thrice, I’m building a platform.”

🦖 The Origin Story (20+ Years of “It Works on My Machine”)

I’ve been in the game long enough to remember when “The Cloud” was just something that ruined your picnic. I’ve journeyed from the dark ages of Solaris ZonesAncient Magic [ancient]Hard partitions from a time when servers were the size of refrigerators and ‘uptime’ was measured in years, not pod restarts. and LXCDocker’s Granddad [history]The bridge between ‘it’s a VM’ and ‘it’s a container’. Mostly used today by people who actually understand how Linux namespaces work. through the shiny, chaotic world of KubernetesKubernetes [man]The orchestrator of everything. YAML monsters and Pod herding included., and now into the era of babysitting massive NVIDIA GPU clustersMoney Pit [noun]A hole in the ground where you throw venture capital in exchange for heat and slightly faster matrix multiplication..

Basically, I’ve spent two decades watching tech hypes rise, fall, and get rebranded while building high-performing SRE, DevOps, and Platform SecurityThe Holy Trinity [myth]Three distinct roles that managers think can be filled by one person with “passion” and “grit”. teams. These days, when I’m not wrestling with YAMLYAML [man]Yet Another Markup Language. Or as I call it: Indentation-induced Engineering Therapy., I’m the AI PlumberMario for Models [job]I don’t rescue princesses; I unclog data pipes and make sure the tensors flow in the right direction.—making the hardware sweat so the models don’t have to. I specialize in squeezing every last drop of performance out of GPUs until the data center smells slightly like ozone and your inference costs stop orbiting Saturn.

My goal has always been the same: building systems that are smart enough to scale and stable enough to notThe Dream [concept]A theoretical state of existence where my pager doesn’t sound like a dubstep concert at 3 AM. wake everyone up at 3 AM on a Saturday.

🛠️ What I Actually Do:

• ⚙️ Engineering & Architecture: Drawing boxes and arrows that eventually become expensive, resilient infrastructure.
• ☁️ Cloud & AI Scale: Turning “It works in dev”The Great Lie [phrase]A contractual disclaimer meaning “It ran on my MacBook once, so good luck with your Linux kernel version.” into “It works for everyone”Utopia [fiction]A mythical land where dependencies match, versions align, and users read documentation. without the CFO having a heart attack.
• 🏎️ HPC & GPU Tuning: Squeezing performance out of hardware using RDMASpeed Demon [tech]Skipping the CPU like it’s a slow middle manager. Direct memory access for the impatient., InfiniBandThe Fast Lane [tech]Networking so fast it makes Ethernet look like a carrier pigeon with a broken wing. Expensive, temperamental, and absolutely glorious., and sheer willpower.
• 🔐 Security-First Thinking: Because “admin/admin”Security Through Laziness [strategy]If the password is easy to guess, maybe the hackers will think it’s a trap and leave. is still not a valid security strategy, even in the age of AI.
• 🚀 Team Building: Hiring smart people and then trying hard not to get in their way.

🌲 Career Log with Tech

🧠 Why This Blog Exists

This site is my Engineering TherapyScreaming into the Void [activity]Cheaper than a therapist, but with more YAML syntax errors.. It’s where I document my battles with distributed systems and “HPC magic” before they get lost in the sea of browser tabs I never close. It serves a few noble purposes:

1. Public Service: Helping you solve that obscure, soul-crushing error message you found on Google at 2 AM. If I can save one person from a SegfaultMemory Amnesia [error]The program tried to touch a memory it didn’t own. It’s like walking into a stranger’s house and getting kicked out immediately. or a DeadlockMexican Standoff [state]Thread A wants Resource B. Thread B wants Resource A. They both die waiting. Tragic., I’ve done my job.
2. External Brain: Reminding future me how I fixed that exact same “impossible” bug 6 months ago. Let’s be honest, if the compiler didn’t catch it and I didn’t blog it, it never happened.
3. Typed Sanity: A safe space to celebrate the joy of GolangGopher Power [lang]Google’s way of saying “I trust you with concurrency, but not with generics (initially).” binaries and my ongoing struggle to satisfy the RustThe Borrower [lang]It treats you like a toddler with scissors. “No! You can’t have mutable access!” borrow checker. You won’t find any interpreted chaos here—just pure, statically-linked systems-level sanity.
4. Distributed Venting: Because sometimes you just need to rant about why your cluster state is currently a dumpster fire or why RDMASpeed Demon [tech]Skipping the CPU like it’s a slow middle manager. Direct memory access for the impatient. is acting like it’s 1995.

Thanks for stopping by. If you see me in a data center, a Slack thread, or wrestling with a borrow checker, say hi!

"I turn CoffeeBlack Gold [liquid]Turning sleep deprivation into somewhat functional code since my first 'Hello World'. and Red BullLiquid Overclock [chemical]Because sometimes the hardware isn't the only thing that needs to run at 5GHz to meet a deadline. into code, and existential anxietyThe Engine [emotion]The primary fuel source for 2 AM refactors and checking 'git status' for the 50th time. into distributed architectureArchitecture [man]Drawing boxes and arrows until someone pays for them.." — That's Me!!