Somasundaram M

Every app on your phone should just be an API endpoint for agents. Karpathy replaced six smart home apps with a WhatsApp bot. Three prompts. The apps became unnecessary overnight. The more you tinker with agents on side projects, the clearer this gets. The UI isn't the product. The capability behind it is. Agents don't need buttons and navigation flows. They need endpoints.

@radnerus93 💯

Though it's called vibe coding, the vibes will match with Agents only when you know what you are doing.

@radnerus93 @claudeai It does do that if ur prompt vaguely hints that we are planning again

Claude Code Feature request: Auto switch to 'plan mode' once the execution and validation is complete in 'accept edits' as per the plan. @claudeai

Lost 4 hours this week because I got lazy with Claude. The task was straightforward. Told it what to do in one high-level sentence. It ran, made changes, I didn't review the reasoning, just waited for the result. Tested manually. Nothing had changed. Turns out Claude solved a different interpretation of the problem. My instructions were too vague to catch it. Started treating it like a junior dev after that. Not "go to the shop and buy an apple." More like "go to the shop, buy one apple, and come back." Explicit steps. Expected output. What NOT to do. The faster the tool gets, the lazier you get with instructions. That's where the bugs hide.

When an agent fails, most engineers switch models. "Claude couldn't do it, let me try GPT." "GPT fumbled, back to Claude." The mindset shift that changed my output: assume it's your setup, not the model. Bad instructions in the AGENTS.md. Missing context. Wrong scope for the task. Karpathy said it on No Priors this week. When things don't work with agents, it feels like a skill issue, not a capability gap. That framing changes how you iterate.

Running multiple coding agents in parallel sounds like a superpower until two of them commit to the same branch and you spend 40 minutes untangling the mess. Switched to git worktrees. Each agent gets its own checked-out copy. No conflicts, no merge chaos. Karpathy talks about tiling 10 codex agents on a monitor. That only works if you've separated the blast radius. Worktrees are the boring fix that makes the flashy workflow actually hold up.

Set up an agent to monitor my email every 6 hours, pull transaction details, parse amounts, and add them to a Google Sheet for budgeting. Forgot about it. Two days later, rows showed up that I didn't add. Karpathy calls this a "claw" on the latest No Priors. Not an agent you sit with. A persistent loop that works while you're not looking. The jump from chatbot to daemon is the shift most people haven't made yet.

@zathvarun oh, interesting for me Ghostty still works well, not even looking back at iTerm.

Switching back to iTerm, feels more stable and native.

Karpathy just dropped one of the best podcast episodes of the year on No Priors. Code agents, AutoResearch, "AI psychosis," why apps should just be API endpoints, model speciation, the job market, and why he hasn't typed a line of code since December. Been processing this for a few days. Got thoughts. More posts coming. youtu.be/kwSVtQ7dziU

Our side project's first cloud bill was way higher than we expected. The instance was running 24/7. We forgot to turn it off. Nobody set a billing alert. Lesson learned: set billing alerts before you deploy, not after. The cloud doesn't care about your intentions. Your wallet does.

The Android dev job market in 2026: Everyone's hiring "mobile engineers." Nobody's hiring "XML layout specialists." Compose, Coroutines, KMP, CI/CD, system design — that's the bar now. If your resume still leads with "proficient in RecyclerView," it's time for an update. The market didn't change overnight. You just didn't notice.

@radnerus93 Depends on what the agent does next with the output. Plain text that the model can parse? CLI works fine. But if you need reliable structured data or auth baked in, MCP earns its context cost.

@msomuin If cli is available for an external API then it's better to use CLI over MCP right?

"MCP is dead. Use CLIs instead." I use both. Every day. MCP for structured external APIs — my task manager, calendar, analytics. The agent needs auth, structured data, state. CLI for everything local — grep, git, jq. Zero-cost context. Models already know Unix pipes. GitHub's MCP server used to cost ~55K tokens just to load. They cut ~23K tokens in January. Still a massive context tax before you ask a single question. The answer was never "MCP vs CLI." It's knowing which one to reach for.

We’ve already shared quite a bit about Air @getsome_air, but one thing we haven’t: it’s built entirely with Kotlin Multiplatform! That means you’ll soon be able to use it in a web browser 🌐 Here, @vdtankov dives into the tech stack powering Air:

Compose adoption hot take: Companies shipping Compose in production aren't the brave ones. Companies starting new features in XML in 2026 are the ones taking the real risk. XML isn't "stable." It's abandoned. Google's investment is in Compose. Betting against the platform owner is the risky move.

Spent 4-5 hours every month manually entering bank transactions into a spreadsheet. Every. Single. Month. Built a Telegram bot with Python + Claude Code that does it in under 5 minutes. Parses statements, auto-categorizes, deduplicates, uploads. The boring automation nobody talks about saves the most time.

Put my Zoom on 'brb', went to water my plants. Three minutes tops. Came back more focused than I'd been all morning. AI agents already handle a lot of the heavy lifting. My output is bottlenecked by my energy now, not my task list. Short breaks between long meetings fix that.

@dibakarrmandal @hamen Life time value of users

@hamen @msomuin What is LTV?

The Android interview question nobody asks: "You have users on Android 11 through 16. Five active OS generations in Asia alone. 2GB RAM phones and foldables running the same APK. How do you ship without breaking either?" That's not a hypothetical. That's Tuesday.

Nobody talks about the nano-texture display on MacBook Pro enough. No glare. No washed-out colors. Just the screen, doing its job. Can't go back to glossy now.

I don't write boilerplate anymore. Claude Code + git worktrees + MCP = I describe what I want, review what it builds. One feature building. Another in PR review. Tests running on a third. My role shifted from typist to architect. The "waiting for Gradle" meme is dead.