Ankush Dharkar

ACTORS + AI: Director/Actor/Producer/Writer AI Chef 🧑‍🍳 Hans Obma visits the Cozy AI Kitchen 🎂 https://lnkd.in/gjiAvEfP to share his insights on how AI has transformed his creative processes. You may have seen Chef Hans in such 📺 hits as Better Call Saul, Wandavision, or Narcos — and yes, he's probably the most handsome AI 🧑‍🍳 chef we've had in the kitchen to date :-). Hans needed to learn a new language ... how did he do it? He got multimodal AI models to help him speak Welsh. Hans needed a way to scale how he communicated with his stakeholders ... how did he do it? He created an authentic-to-him way of scaling by creating an instant entourage of supporting agents. HT 🧑‍🍳 Ross Heise 🧑‍🍳 Matt Scholz and the power of the Wisconsin network for bringing such a storied talent to the Cozy AI Kitchen! --- This 🍰 episode: https://lnkd.in/gjiAvEfP All 50 episodes: https://lnkd.in/g6upvbGX

89

11 Comments

🌐 Introducing TalkAPI.ai where any API becomes a conversation. Ever wished you could just talk to an API ,instead of reading endless documentation? Now you can. Upload any API doc or paste a URL, ask your question in plain English, and get a ready-to-run code snippet in seconds. That’s the magic of TalkAPI.ai ✨ 🎥 Watch the short videos below to see how it works — From documentation ➜ to code ➜ to execution. All in one place. 🚀 Try it today: www.TalkAPI.ai #AI #APIs #Automation #TalkAPI #Innovation #SaaS #Developers #NoCode #TechTools

Protect Claude Code's Context. Thank Me Later.  I think of Claude Code's context window like a brain. And you can quietly destroy it by letting bad messages pile up. Garbage in, garbage out. Two tricks I use daily.                                                                                                                                                                                   Trick 1: ESC and Time Travel                                                                                 Short drifts are fine, let them play out. But the moment you notice Claude has been going the wrong direction for a while, hit ESC. Don't let it finish. Scroll back to your original message, rewrite it with more clarity, and this time add a hint about the exact wrong path it took. You just stopped a thread of bad thinking from living in your context permanently.      Trick 2: ESC, Distill, Clone, Resume                                                                             When debugging gets messy and Claude goes down five tangents before finding the answer, stop it. Ask it to distill everything into a markdown file. Clone that file so time travel won't erase it. Then resume before your original message and attach the file as context.                                                                                             Clean slate. Right answer. No tangent graveyard.                                        #ClaudeAI #VibeCoding #SoftwareEngineering #AITools #DeveloperProductivity #BuildInPublic

7

This is the current gold standard of vibe coding. Having an orchestrator to spawn subagents to explore different aspects simultaneously, and using parallel tool calls. Details see: https://lnkd.in/gCvNbXrX

5

2 Comments

The circles of Control, Influence, and Concern Early in our careers, we’re often told to “own the outcome.” As we grow, that ownership broadens beyond code or systems — it extends into people, mechanisms, and culture. Stephen Covey’s Circles of Control, Influence, and Concern provide a simple but powerful framework for reflection — one that we all live through daily. Circle of Control This is what you can directly act upon — your code, design quality, and decisions. It’s where you move fast because you don’t need permission to do what’s right for the system. For me, this means writing tenets, defining metrics, reviewing designs, and raising the bar on engineering standards. Circle of Influence This is where leadership without authority matters. You can’t force a change here — but you can shape it. Influence is built through clarity, trust, and data. When you help another org simplify a design, mentor an SDE into a stronger reviewer, or align leaders on shutting down a misaligned project — you’re operating here. Your success depends not on hierarchy, but on how consistently you demonstrate judgment, objectivity, and customer obsession. Circle of Concern This includes everything you care about but can’t control — like organizational priorities, macro-level business shifts, or leadership changes. The key here is emotional discipline. Those who spend energy worrying about concerns they can’t act on end up drained. Those who channel that energy back into influence — writing a clear doc, proposing a mechanism, or building alignment — create impact. Success isn’t about controlling everything; it’s about knowing where to invest your judgment, where to build trust, and where to let go. How do you decide which circle your current challenge belongs to?

34