Welcome back to TechTalks with Manoj — where we stop treating AI like autocomplete and start designing workflows like it actually understands our systems.

Today’s topic: GitHub Copilot CLI — and why the terminal is quietly becoming the most powerful AI interface in modern development.

For years, the IDE has been the center of gravity. That’s where intelligence lived — code suggestions, linting, debugging. But as systems grew into monorepos, microservices, and distributed architectures, the IDE started showing cracks. Too much context, too many moving parts, and not enough visibility into the system as a whole.

Now something interesting is happening.

AI is moving out of the editor… and into the terminal.

And that changes everything.

Because the terminal isn’t just where you write code — it’s where you run systems, inspect logs, manage infrastructure, and orchestrate workflows. When AI lives there, it stops being a helper… and starts becoming an operator.

In this episode, we’ll break down what GitHub Copilot CLI really is — beyond the marketing. We’ll look at how agentic workflows are reshaping development, why context-aware systems like MCP are the next step, and where this all fits into real-world architecture.

We’ll also talk about the risks — because blindly trusting AI in your terminal is a very efficient way to break production faster than ever before.

If you’re still thinking of AI as a coding assistant, this episode might change how you see your entire development workflow.

Let’s get started. 🎙️

Thanks for reading! Subscribe for free to receive new posts and support my work.

Welcome back to TechTalks with Manoj — where we stop pretending distributed systems are simple and start designing them like they’re not.

Today’s topic: Cloud Storage—beyond the infinite bucket.

On a slide, storage is the easiest part of the stack. You drag a “bucket” icon, point your app at an endpoint, and assume it’s someone else’s problem. But in production, storage is where data gravity anchors your budget, where IOPS throttling creates ghost latencies in your DBs, and where a “simple” archival strategy turns into a 15-hour waiting game for a single critical file.

We’re going to look at the architectural trade-offs between Azure and AWS that actually impact your uptime. We’ll talk about why S3’s “intelligent tiering” can be a trap for small files, how Azure’s Hierarchical Namespace changes the game for Big Data, and why provisioning storage performance is the one lever that will either save your performance or bleed your bank account dry.

If you’re building systems that have to survive data corruption, massive egress fees, and the brutal reality of multi-petabyte scale—not just a Todo-list demo—this episode is for you.

Let’s get started. 🎙️

Thanks for reading! Subscribe for free to receive new posts and support my work.

Welcome back to TechTalks with Manoj — where we stop pretending distributed systems are simple and start designing them like they’re not.

Today’s topic: message queues beyond the basics.

On diagrams, they look clean — producers, brokers, consumers, done.In production, they’re where consistency breaks, lag grows silently, and “exactly-once” turns out to mean “almost never.”

We’ll talk about delivery guarantees that actually matter, why idempotency is non-negotiable, how the outbox pattern saves you from data corruption, and when exactly-once is worth the cost — and when it absolutely isn’t.

If you’re building systems that have to survive retries, failures, and real traffic — not demos —this episode is for you.

Let’s get started. 🎙️

Thanks for reading! Subscribe for free to receive new posts and support my work.