---
title: "Mukul Kumar (@pydevgo) | Hashnode"
description: "Engineering deep dives into system design, distributed systems, and the trade-offs behind real-world technology."
url: "https://hashnode.com/@pydevgo"
---

@pydevgo

# Mukul Kumar

@pydevgo · Joined October 2026

Engineering deep dives into system design, distributed systems, and the trade-offs behind real-world technology.

### [Starlink's 2.5-Hour Global Outage: The Core Network Failed, Not the Satellites](https://buildopsy.hashnode.dev/starlink-2-5-hour-global-outage-core-network-failure?utm_source=hashnode&utm_medium=feed)

An analysis of Starlink's 2.5-hour global outage. How ground core control planes create single points of failure for LEO satellite networks.

4 min read · [buildopsy.hashnode.dev](https://buildopsy.hashnode.dev/starlink-2-5-hour-global-outage-core-network-failure?utm_source=hashnode&utm_medium=feed)

[8h ago](https://hashnode.com/posts/starlink-2-5-hour-global-outage-core-network-failure/6af335c50dfe9f9020feb197)

### [Why a 30-Second EC2 Job Bills Twice Its Runtime (and Two Other Hidden Meters)](https://buildopsy.hashnode.dev/why-a-30-second-ec2-job-bills-twice-its-runtime-and-two-other-hidden-meters?utm_source=hashnode&utm_medium=feed)

Worked US East EC2 math: how the 60-second floor doubles 30s batch jobs, why partial Capacity Reservations bill idle slots, and EBS/T3 fees.

3 min read · [buildopsy.hashnode.dev](https://buildopsy.hashnode.dev/why-a-30-second-ec2-job-bills-twice-its-runtime-and-two-other-hidden-meters?utm_source=hashnode&utm_medium=feed)

[1d ago](https://hashnode.com/posts/why-a-30-second-ec2-job-bills-twice-its-runtime-and-two-other-hidden-meters/6af15e75b63642dde6697a32)

### [When S3 Request Fees and the 128 KiB Floor Outgrow Your Storage Bill](https://buildopsy.hashnode.dev/s3-request-fees-and-128-kib-minimum-object-size?utm_source=hashnode&utm_medium=feed)

Worked US East S3 math: how 100M GETs ($40) outgrow 1 TiB storage ($23.55), and why Standard-IA and Glacier Instant bill a 128 KiB floor.

4 min read · [buildopsy.hashnode.dev](https://buildopsy.hashnode.dev/s3-request-fees-and-128-kib-minimum-object-size?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/s3-request-fees-and-128-kib-minimum-object-size/6aefa7bda2604b31b2b2efe5) [3d ago](https://hashnode.com/posts/s3-request-fees-and-128-kib-minimum-object-size/6aefa7bda2604b31b2b2efe5)

### [A package name from a code model is still an untrusted dependency](https://buildopsy.hashnode.dev/slopsquatting-ai-package-hallucinations?utm_source=hashnode&utm_medium=feed)

Are AI-generated code dependencies a real security risk?

2 min read · [buildopsy.hashnode.dev](https://buildopsy.hashnode.dev/slopsquatting-ai-package-hallucinations?utm_source=hashnode&utm_medium=feed)

[Nov 2](https://hashnode.com/posts/slopsquatting-ai-package-hallucinations/6ae81440f4b618f8a8c1a968)

### [How Discord’s Message Storage Hit a Scaling Wall](https://buildopsy.hashnode.dev/how-discord-s-message-storage-hit-a-scaling-wall?utm_source=hashnode&utm_medium=feed)

Explore Discord's messaging architecture, Cassandra data modeling, hot partitions, and the trade-offs behind storing trillions of messages at scale.

4 min read · [buildopsy.hashnode.dev](https://buildopsy.hashnode.dev/how-discord-s-message-storage-hit-a-scaling-wall?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/how-discord-s-message-storage-hit-a-scaling-wall/6ad2f7ca9fb50037f2bb17d7) [Oct 17](https://hashnode.com/posts/how-discord-s-message-storage-hit-a-scaling-wall/6ad2f7ca9fb50037f2bb17d7)