suren

Tips for contacting someone through DMs: - Greet them - Introduce urself - State problem - Mention the required outcome - Mention the steps you have taken so far - Important - If they are busy, send a humble reminder #DEVCommunity here is awesome, use it wisely. #100DaysOfCode

@msomuin @claudeai Oh nice! I will try tweaking the plan accordingly

@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

@zathvarun Ghostty + bg loading of omz is the sweet spot for me. Ghostty feels even more stable after the latest update.

Switching back to iTerm, feels more stable and native.

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

@msomuin Cool idea! Gonna try this weekend.

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.

Do you remember when you joined X? I do! #MyXAnniversary

@msomuin Fair enough!

@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.

"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.

@akadhanu @X I think no😁

@X is down?

@akadhanu @claudeai Yup! It's difficult to get back into the flow state again.

@radnerus93 @claudeai Things happen, when all are in same track 🫠

Middle of my flow state and @claudeai is down 🤦‍♂️

Also, we need to know which model to use where, how to streamline memory for continuous process, and more. Ppl start putting in the latest and greatest model into work and thinking it won't make mistakes is really silly - will it work? Yes. But is it needed is the real question.

@radnerus93 True. Distribution of AI is wide, but depth of implementation is still catching up. The gap between demo and production is where most teams struggle.

I see a wide range of areas in IT where AI is employed. When I look closer at how it is implemented, I see a lot of holes. Sad, but true!

Pro tip: Use MCP (Model Context Protocol) like the USB-C of AI—secure handoffs or your swarm turns into a group chat from hell.

@radnerus93 Absolutely discernment beats blind adoption every time

Knowing when not to use AI is the new super power.

What do you guys do while Claude Code is “thinking”?

Agent refactoring truth: the code Agents wrote for your microservice works… until it doesn’t. If you can’t debug it without the prompt history, you didn’t build software — you built debt.

Ever felt like AI is sucking the joy out of tech, leaving you exhausted, anxious, and one step behind no matter how hard you try? I've been watching @NetworkChuck for a long time now, drawn in by his killer content on all things tech—especially his deep dives into AI and hacking AI systems. He's got this way of breaking down complex stuff that just clicks, from ethical hacking tips to the wild world of AI tools. His latest video "I kind of hate AI" (youtu.be/dbMXi9q78Tk) literally spoke my mind. The burnout from chasing every new AI trend, the anxiety of feeling like you're always playing catch-up, the overwhelming pace of it all... it's exactly what's been rattling around in my head lately. Chuck nails the frustration without hating on the tech itself—it's more about the hype cycle wearing us down. If you're in tech and feeling this too, give it a watch. It's refreshing to hear someone call it out honestly. And hey, that overwhelming feeling and anxiety? It might actually be a good kind of vibe—proof you're still deeply invested and pushing yourself in this fast-moving space. What's been on your mind lately?

Submitted a CFP for ChennaiFOSS 2026 🎤 “Open Source Licensing for Developers: Avoiding Legal Landmines” A practical look at MIT, Apache, GPL and the common licensing mistakes developers make when using open-source code. fossunited.org/c/chennai/2026… @FOSSChennai @IndiaFOSS