Follow me to learn how you can leverage AI to boost your productivity and accelerate your career. Scaled products to 8 Million+ users and built the world's biggest AI newsletter with 1 Million+ readers.

Zain Kahn

This guy from Cambridge plays with Claude Code like he owns it.

He talks about his workflow in 2026 and here's what's new: 

1. Video-Based Specification (Spec Phase)

> Screen Recording: 

Instead of writing a spec from scratch, find an existing product that is similar to your idea. Record your screen while using it and talking through your specific feature ideas and changes.

> Generate PRD: 

Upload this video to Gemini 1.5 Pro (referred to as Gemini 3 Pro/Free Pro in the video context) and ask it to generate a Product Requirement Document (PRD).

> Refine Spec: 

Use the "Ask User Question" tool in Claude Code. Prompt it to interview you about the generated spec to fill in missing details (e.g., "How should the emoji picker be positioned?").

> Package Discovery: 

Feed the refined spec into ChatGPT with "Heavy Thinking" (likely OpenAI's o1/o3 models) to search for and recommend specific, well-maintained GitHub packages (e.g., for a WYSIWYG editor) to avoid building complex components from scratch.

2. The Orchestrator Role

> Design Feedback Loops: 

Your primary job is not to write code but to design loops where the agent can build, fail, and learn.

> Monitor & Update: 

Watch the agent’s reasoning. If it makes a mistake, don't just fix the code—update the claude. md (project instructions file) to prevent that specific mistake from happening again.

> High-Level Decisions: 

Make the architectural decisions the agent can't, such as choosing the database or specific tools.

3. Model Choice & Tools

> Model Selection: 

Use Opus 4.5 for building large-scale features and GPT-5.2 for architecture and debugging (specific future models mentioned in his 2026 context).

> Voice Dictation: 

Use HyperWhisper to dictate prompts significantly faster than typing.

4. Execution & "Parallel Vibe Coding"

> Parallel Agents: 

For small, well-defined tasks (like extracting hard-coded strings for translations), spin up multiple sub-agents to work on different parts of the project simultaneously.

> Avoid Conflicts: 

Do not use parallel agents for large features within the same project to avoid complex merge conflicts ("meshing issues").

> Sub-agents for Multi-Project Fixes: 

If a bug exists in a template used by multiple projects, spin up one sub-agent per project to fix them all in parallel.

5. Review & Maintenance

> Planning Mode: 

Use Claude Code’s "Planning Mode" to prevent Architectural Drift, ensuring the agent sticks to the original design vision over time.

> Shape of Diffs: 

Inspect the "shape" of the code changes (diffs) to ensure they are manageable and align with expectations before accepting them.

> Forking for Learning: 

If the agent does something surprising or complex, fork the session. In the forked session, ask "Why did you do that?" or request diagrams to understand the code without polluting the context of the main working session.

Get more tutorials here: https://lnkd.in/e64Jvdrt

Follow me to learn how you can leverage AI to boost your productivity and accelerate your career. Scaled products to 10 Million+ users.

Traditional computer science degrees can't keep up with this pace.

Here are the 15 engineering blogs that actually teach real-world scale:

1 → THE CODE
Scale at global level.
Teaches you how to code with AI and AI Agents
https://lnkd.in/e64Jvdrt

2 → Airbnb Tech Blog
Product engineering done right.
User focused systems.
https://airbnb.tech/blog/

3 → Meta Engineering
Billions of users infrastructure.
Performance at extreme scale.
https://engineering.fb.com

4 → AWS Architecture
Cloud design patterns revealed.
Production ready blueprints.
https://lnkd.in/gqjh88PS

5 → Netflix TechBlog
Streaming at massive scale.
Chaos engineering explained.
https://lnkd.in/gNE8Cs6Z

6 → Discord Engineering
Real time systems mastery.
Handling millions of connections.
https://lnkd.in/gea6kSwt

7 → Google Research
Cutting edge tech breakthroughs.
Tomorrow's solutions today.
https://lnkd.in/gjzDu8wp

8 → NVIDIA Developer
GPU powered computing insights.
AI infrastructure secrets.
https://lnkd.in/dt_BW7qF

9 → Slack Engineering
Collaboration platform internals.
Distributed systems at scale.
https://slack.engineering

10 → Cloudflare Blog
Internet infrastructure deep dives.
Security and performance wins.
https://lnkd.in/gqa-HE6h

11 → Figma Tech Blog
Collaborative design systems.
Browser performance magic.
https://lnkd.in/g2KF_eX9

12 → Shopify Engineering
E-commerce at scale.
Black Friday traffic handled.
https://lnkd.in/g7DVzRAc

13 → Stripe Engineering
Payment systems that work.
Financial infrastructure explained.
https://lnkd.in/gfMr-jEr

14 → Microsoft Engineering
Enterprise scale solutions.
Developer tools insights.
https://lnkd.in/g3Mi8XES

15 → GitHub Engineering
Code collaboration at scale.
Developer platform secrets.
https://lnkd.in/gPHaD6AC

16 → Bonus
System design deep dives.
https://lnkd.in/g-tP7eEc

Save this for later.
Repost ♻️ for aspiring engineers.

Follow me for more AI playbooks and engineering resources.

Claude Code is only as good as your orchestration workflow.

I spent 6 months testing it so you don't have to. 

[ P.S. You can get my Ultimate Claude Code guide for engineers here at no cost: https://lnkd.in/e64Jvdrt ]

So Boris Cherny (the creator of Claude Code at Anthropic) recently shared the internal best practices his team actually uses daily. 

Someone brilliantly distilled those threads into a structured CLAUDE .md file you can drop straight into any project root.

It acts as a system prompt. Turns Claude into a far more autonomous, rigorous engineering partner.

Here's what it does:

→ 𝗪𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝗢𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻: Mandates "Plan Node Default" for any task over 3 steps. Uses subagents liberally to keep the main context window clean.

→ 𝗦𝗲𝗹𝗳-𝗜𝗺𝗽𝗿𝗼𝘃𝗲𝗺𝗲𝗻𝘁 𝗟𝗼𝗼𝗽: This is the real magic. After ANY correction, it updates a tasks/lessons .md file. You're building a compounding system where the mistake rate drops over time because it actively learns from your feedback.

→ 𝗩𝗲𝗿𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗕𝗲𝗳𝗼𝗿𝗲 𝗗𝗼𝗻𝗲: Can't mark a task complete without proving it works. Diffs behavior. Runs tests. Checks logs. The bar? "Would a staff engineer approve this?"

→ 𝗔𝘂𝘁𝗼𝗻𝗼𝗺𝗼𝘂𝘀 𝗕𝘂𝗴 𝗙𝗶𝘅𝗶𝗻𝗴: Zero hand-holding. Point it at failing CI tests or error logs... it just goes to work. No constant context switching from you.

→ 𝗦𝘁𝗿𝗶𝗰𝘁 𝗧𝗮𝘀𝗸 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁: Forces a "Plan First" approach written to a todo .md with checkable items before any implementation starts.

And perhaps the most important part?

It forces the AI to prioritize simplicity, find root causes instead of temporary fixes, and minimize the blast radius of every change. Senior developer standards. Not shortcuts.

If you're spending hours a day in the terminal with AI, setting up a strong .md instruction file like this isn't optional anymore. It's the difference between AI that drifts and AI that compounds.

It takes time to set up. But if you do, you're ahead of almost everyone else.

Lemon is the most powerful tool I've used since ChatGPT.

You literally say things with your voice and it does it for you instantly.

Pure magic.

Michael Pedersen

Revenue Growth | Emotion-Based Brand Messaging To 3x Your Revenues | Bridging the gap between sales and marketing

High call-volume teams don’t fail from lack of skill.They lose performance across the shift when rough calls stack and recovery lags the next dial.Morning numbers are strong.Afternoons drift.DecideFast™ runs in the seconds after a call so performance holds from first block to last.No integration.No coaching.No training.No workflow changes.No IT involvement.Training happens before the shift.Coaching happens after the shift.Dashboards explain the drop once it already hit the numbers.Nothing protects the transition between one call and the next.That is the gap DecideFast™ fills.DecideFast™ shortens after-call transition so the day doesn’t slide as it progresses.Used in seconds.No management overhead.See after-call recovery live.No slides. No pitch.

CEO & Founder

Does your website convert? When was the last time you gave it a refresh? How does it compare to your competitors?

Your company website is your brand on the Internet. An under-performing and outdated website will cost you revenues. 

Let’s jump on a discovery call to see if we are good fit to work together 

Visit: www.AZNetmarketing.com or 
Email: mike@aznetmarketing.com

Most phone sales “burnout” isn’t burnout.

It’s compounding.

A rough call ends.
The rep logs it.
The dialer fires the next one in seconds.

➡️ Nothing clears what just happened.

By the third or fourth tough call in a row, tone tightens. Close attempts lose edge. Response speed slows just enough to matter.

Morning block looks strong.
Afternoon block drops.
Same script. Same leads. Same rep.

What changed?

Not energy.
Not motivation.
How fast they bounce back after a rough call.

If it takes 3-4 calls to get back to normal, the afternoon is gone.
If it takes 1, the day holds.

➡️ Training builds skill.
➡️ Coaching fixes patterns.
➡️ Dashboards show the drop.

But the real break point lives between calls, or more specifically after a rough one.

That’s where the afternoon is won or lost.

The gap is the 5-8 seconds after a rough call when the next dial starts and they're still carrying the last one. 

You don't need to make them better salespeople. You need to help them start the next call without dragging the last one into it.

➡️ 14-day, 25 rep contained pilot. 
➡️  Does afternoon output hold.
➡️  Email me: mike@decidefastbusiness.com

#insidesales #phonesales #salesmanagement

Mike Pedersen

High-Volume Phone Teams See Afternoon Performance Drop | Between-Calls Reset Software Prevents It | No Training. No IT. No Workflow Changes.

I spent an hour reading call center Reddit threads.

Reps aren't complaining about their CRM. They're not asking for more training. They're not asking for better scripts.

Here's what they're actually saying:
➡️ "We need 1-2 minutes between calls. This shit is not right."
➡️ "Back to back calls with no time to recover - even 5 minutes without one was rare, and when it happened I felt relieved."
➡️ "Our after-call time is 10 seconds. If we had 3-5 minutes between calls it would be way more bearable."
➡️ "Max allowed between calls is 4 seconds."
➡️ "I literally have 5 SECONDS between calls. It's hell."

The problem isn't the calls.
It's what happens between them.

Notice what they're NOT asking for: More coaching. More training. Better tools.
They need recovery between calls. That's it.

How long do we keep normalizing this?

🚫 A 100-rep team losing 30% output after lunch is burning $1.2M+ annually in wasted payroll. Same people. Same pay. 70% productivity.

Companies are paying for coaching platforms they don't use. Training programs they forget. Software they ignore.

🚫 Meanwhile, the actual problem costs companies $1.2M per 100 reps. Every year.

They pay for 8 hours, and get 5.5 hours of output. Every day. Every month. Every year.

➡️ 14-Day, contained tests. Your data. Your choice. Contact me if you want to stop normalizing this.

The One Moment No Phone Sales Tech Stack Covers

There is a single moment in the phone sales day that explains why performance breaks even when everything looks right.

➡️ Between-Calls Performance Stability

➡️ It is the only moment no system owns.
Dialers move the next call. CRMs log the last one. Nothing is responsible for what carries from one interaction into the next.

➡️ It is the only moment managers cannot scale into.
A manager can step in after the damage is visible. They cannot be present in the seconds between every call across dozens of reps.

➡️ It is the only moment dashboards cannot see.
Dashboards show outcomes after execution already changed. They never show the hesitation, tone shift, or pace decay forming between calls.

➡️ It is the only moment where one interaction affects the next.
A harsh rejection does not stay isolated. Without clearing, it alters the next conversation, then the next, then the next.

➡️ It is the only moment that explains same-day instability without blaming reps.
The capability is proven in the morning. The breakdown happens later because carryover compounds, not because reps forgot how to sell.

That moment sits between calls (5-8 seconds).

DecideFast™ is the between-calls sales performance software for phone-based sales teams, designed to prevent performance decline throughout the day. 
Not training. Not coaching. No IT lift. No workflow change. Sits alongside your dialer, CRM, QA, and coaching.

Used in the seconds after a tough call to clear the carryover fast and maintain dial pace and next call success.

➡️ We are executing low-risk, 14-day, 25-rep contained tests to stabilize afternoons for phone sales teams. 

Let's talk if you want to hit your afternoon numbers and have your managers intervening less

If your sales reps make 60 to 100 calls a day, read this. ⬇️ 

If you run a phone sales team, you already know this.

Mornings feel steady.
By mid-afternoon, you are pulling reps aside, calming people down, resetting tone.

You are not coaching skill.
You are managing carryover.

You've already invested in training and coaching. That's not the gap.

The gap is the 5-8 seconds after a rough call when the next dial starts and they're still carrying the last one. 

You don't need to make them better salespeople. You need to help them start the next call without dragging the last one into it.

➡️ 14-day, 25 rep contained pilot. 
➡️  Does afternoon output hold.
➡️  Email me: mike@decidefastbusiness.com

30–45% annual attrition in phone sales. 20–40% afternoon output decline.

Every year. Every floor. Industry-wide.

If a manufacturing plant lost 35% of its operators annually and produced 25% less output after lunch, the operation would be shut down.

In phone sales, it gets a line item in the budget.

Detection would follow measurement. If afternoon throughput consistently runs 20 percent below morning throughput, that pattern would be identified, named, and quantified. Not absorbed. Not averaged away. Named as a recurring condition with a measurable cost. 

Nobody caused this. Nobody's proud of it. But everybody normalized it.

The question worth asking isn't who's responsible. It's why the industry stopped looking for a solution.

I wrote something every phone sales leader should read — and pass to their CFO.

Read it here: https://lnkd.in/gT8ssJaE

What is rough call carryover.

Most leaders call it burnout.

Morning block looks sharp.
Afternoon block widens.
Same reps. Same leads. Same scripts.

What changed?

After a stretch of tough calls, hesitation between dials stretches.
Five seconds becomes eight.
Eight becomes twelve.
Across a team, that compounds fast.

That’s not exhaustion.
It’s rough calls accumulating.

Definition of Rough Call Recovery: The ability of a phone sales rep to return to normal pace and tone before the next dial after a rough call.

I wrote a breakdown on what it is and how to spot it in your numbers.
https://lnkd.in/gycdm6eq

If you are a phone sales leader and you want to stop your afternoons from crashing, there is a way. And it's not in your current tech stack.

➡️ 14-day, 25 rep contained pilot. 
➡️  Measure: Does afternoon output hold.
➡️  Email me: mike@decidefastbusiness.com

taplio

The Battle

Zain Kahn

Michael Pedersen

Followers

Posts

Engagements

Likes

Performance ScoreZain Kahn's LinkedIn Performance

Performance ScoreMichael Pedersen's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Zain Kahn

Michael Pedersen

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Zain Kahn's LinkedIn Performance

Performance ScoreMichael Pedersen's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreZain Kahn's LinkedIn Performance