# Aditya Chowdhry > Engineer, builder and founder interested in how thoughtful systems, teams and AI can make complicated things feel simple. Aditya Chowdhry is a software engineer and co-founder of KoshaX. He has built product, growth, backend and platform systems at Probo, Gojek and Urban Company, and writes Thoughtful Engineering. Based in Gurugram, India. Every post is available as Markdown by adding `.md` to its URL. The full text of all posts is at /llms-full.txt. ## About - [About Aditya Chowdhry](https://www.adityachowdhry.me/about): background, work history and principles - [KoshaX](https://koshax.com): the AI assistant he is currently building - [X](https://x.com/adityachowdhry9) - [LinkedIn](https://www.linkedin.com/in/adityachowdhry09) - [GitHub](https://github.com/aditya-chowdhry) ## Series: Cricket Scale - [Introducing the Cricket Scale Series](https://www.adityachowdhry.me/writing/introducing-the-cricket-scale-series.md): In India, a cricket match is a stress test. What we learned keeping Probo up through it. - [Cricket Scale, Part 1 — EC2 vs Kubernetes](https://www.adityachowdhry.me/writing/cricket-scale-part-1-ec2-vs-kubernetes.md): EC2 autoscaling was too slow for match-day spikes and Kubernetes wasn't ready. So we built a switcher. - [Cricket Scale, Part 2 - Redis: A Silver Bullet With a Cost](https://www.adityachowdhry.me/writing/cricket-scale-part-2-redis-a-silver.md): Redis kept p99 under 100 ms at peak. It also hid our tech debt, until it didn't. - [Cricket Scale, Part 3 - The Not-So-Technical Grind](https://www.adityachowdhry.me/writing/cricket-scale-part-3-the-not-so-technical.md): The biggest wins came from deleting APIs, trimming features and writing match-day playbooks. ## Scale - [Cricket Scale, Part 3 - The Not-So-Technical Grind](https://www.adityachowdhry.me/writing/cricket-scale-part-3-the-not-so-technical.md): The biggest wins came from deleting APIs, trimming features and writing match-day playbooks. - [Scaling with Karpenter: The Good and The Bad](https://www.adityachowdhry.me/writing/scaling-with-karpenter-the-good-and.md): Karpenter in 2023: nodes in 40 seconds instead of 2 minutes, 40% cheaper compute, and a lot of IAM pain. - [Cricket Scale, Part 2 - Redis: A Silver Bullet With a Cost](https://www.adityachowdhry.me/writing/cricket-scale-part-2-redis-a-silver.md): Redis kept p99 under 100 ms at peak. It also hid our tech debt, until it didn't. - [Scaler: our in-house scaling solution](https://www.adityachowdhry.me/writing/scaler-our-in-house-scaling-solution.md): A shared Google Calendar and an Airflow DAG let marketing schedule our infrastructure scaling. - [Cricket Scale, Part 1 — EC2 vs Kubernetes](https://www.adityachowdhry.me/writing/cricket-scale-part-1-ec2-vs-kubernetes.md): EC2 autoscaling was too slow for match-day spikes and Kubernetes wasn't ready. So we built a switcher. - [Introducing the Cricket Scale Series](https://www.adityachowdhry.me/writing/introducing-the-cricket-scale-series.md): In India, a cricket match is a stress test. What we learned keeping Probo up through it. - [How we scaled our Monolith to execute 250Mn+ trades in a day?](https://www.adityachowdhry.me/writing/how-we-scaled-our-monolith-to-execute.md): How about 30 engineers kept Probo on one monolith from zero to 250Mn+ trades a day, and what it cost us. ## AI agents - [Relay: A Control Plane for Agent Work](https://www.adityachowdhry.me/writing/relay-a-control-plane-for-agent-work.md): Human approval, bounded briefs and context layers for supervising multi-agent software work. - [Why I'm Building an AI Assistant in the Age of Giants](https://www.adityachowdhry.me/writing/why-im-building-an-ai-assistant-in.md): Google plays by different rules on Android. Why I'm building an assistant for India anyway. - [The Joy of Coding](https://www.adityachowdhry.me/writing/the-joy-of-coding.md): I don't type most of my code anymore. The joy was never in the typing. ## Craft - [When the CLI Felt Like Magic](https://www.adityachowdhry.me/writing/when-the-cli-felt-like-magic.md): Heroku, the AWS CLI, K9s and Claude Code: from exposing complexity to structuring it. - [Software Engineering: Living With Uncertainty](https://www.adityachowdhry.me/writing/software-engineering-living-with.md): Tools come and go. What compounds, what doesn't, and how to last in a career built on change. - [Thinking in Systems: A Builder’s View](https://www.adityachowdhry.me/writing/thinking-in-systems-a-builders-view.md): A fraud rule engine that paid off, a meme engine that didn't, and knowing the difference. ## Teams - [The Self-Aware Team](https://www.adityachowdhry.me/writing/the-self-aware-team.md): Teams that know the why, the ideal state and the trade-offs don't wait to be told what's next. - [Democratizing Ownership: The Secret to Scalable Teams](https://www.adityachowdhry.me/writing/democratizing-ownership-the-secret.md): Why the same few people always answered the alerts, and how we made reliability everyone's job. - [Platform Teams and the Developer Experience Gap](https://www.adityachowdhry.me/writing/platform-teams-and-the-developer.md): Internal platforms succeed or fail on developer experience. Treat it as the core product. - [Platform Teams: Avoid Becoming a Catch-All](https://www.adityachowdhry.me/writing/platform-teams-avoid-becoming-a-catch.md): Long feedback loops, becoming the bottleneck, becoming the dumping ground, and what helped. ## Optional - [Full text of every post](https://www.adityachowdhry.me/llms-full.txt) - [RSS feed](https://www.adityachowdhry.me/rss.xml)