Ayush

Senior Backend & Cloud Engineer | Shipping GenAI into Production | Creator of unwreck (Ctrl+Z for AI coding agents)

[Ayush @ayushdoesdev]

Block just dropped a voice AI that runs fully local on a MacBook and sounds scarily human.

We’re one good open-source model away from every phone having a real-time AI companion that never phones home.

Who’s actually ready for that?

[Ayush @ayushdoesdev]

Good Saturday to everyone who needed this reminder:

You’re doing better than you think.

Drop a ❤️ if you’re claiming a good weekend.

[Ayush @ayushdoesdev]

Banks are blocking AI agents from customer accounts because people keep handing over their passwords.

This isn’t an “AI gone rogue” story. It’s a systems design failure.

If your agent needs raw credentials, you’ve already lost. Build for scoped permissions, verifiable agent identity, audit trails, and explicit confirmation on money moves.

Least privilege > vibe-coding your way into a transfer.

[Ayush @ayushdoesdev]

Cursor just let AI agents control your entire computer.

Anthropic launched Claude Duet — an agent that keeps working after you close your laptop.

Agents are already writing over half the code at some companies.

The shift from “AI assistant” to “AI employee” just happened.

Most people still haven’t noticed.

[Ayush @ayushdoesdev]

The silent bill is worse than the 3AM page because by the time you notice, the damage is already done. AI will confidently tell you the key is “in the env” while still shipping it straight into the client bundle. Checking for sk_ / service_role + confirming RLS is on is the bare minimum before any public launch.

[Ayush @ayushdoesdev]

Vibe coding gets you to v1 in a weekend.

Then production asks:
• What happens at 10x traffic?
• Why is the API key in the frontend?
• Where are the backups?

AI writes the code.
Someone still owns the 3 AM page.

Who's on call for your vibe-coded app? 💀

[Ayush @ayushdoesdev]

iPhone Duo just dropped today — Apple’s first foldable — and they immediately reclaimed the title of world’s most valuable company.

$1,999 starting price. 7.6" inner screen + 5.4" outer. Titanium. Nano-texture to hide the crease.

Years after Samsung, is this the one that finally makes foldables mainstream… or still a $2k gimmick?

Thoughts? 👇 #iPhoneDuo #Apple #Tech

[Ayush @ayushdoesdev]

AI Agents in 2026: How Small Businesses Can Automate Work and Grow Smarter

👉 https://t.co/CvD1yRMgXm

This article connects a current AI trend to practical business use cases, explains the risks, and naturally introduces AKS Techies' services without turning the post into a sales pitch.

#GenerativeAI #BusinessGrowth

[Ayush @ayushdoesdev]

@runshipcheck Solid minimum. I’d add a free-tier error tracker (Sentry or GlitchTip) so you get the actual stack trace instead of just “site is down”, plus a quick check that no API keys are sitting in the client bundle. Those two catch a lot of the remaining 3 AM pages.

[Ayush @ayushdoesdev]

Anthropic's own data: junior tech hires dropped from 27% to 9% in a year.

Meanwhile, software job postings are up 15%.

So AI isn't killing engineering jobs.

It's killing the entry door.

If nobody hires juniors today, who becomes the senior engineer in 2030?

[Ayush @ayushdoesdev]

AI coding agents are great until one runs `rm -rf` on files Git never tracked.

unwreck is Ctrl+Z for Claude Code, Codex & Gemini CLI.
Local snapshots of your whole working tree (untracked files included). One command rolls back the last turn.

⌘ cargo install unwreck

No cloud. No .git changes.

Check it out: https://t.co/thHcXe8aAV

[Ayush @ayushdoesdev]

Dependency bumps: the scariest PRs with the smallest diffs.

One version number changes.

Thousands of lines of someone else's code changed under you.

That's why I'm building Verspect: see what an upgrade actually changes before you merge it.

How do you vet upgrades today?

[Ayush @ayushdoesdev]

Added an index. Query still slow.

Usual suspects:

• Composite index, wrong column order
• A function on the column: WHERE LOWER(email) = ...
• Leading wildcard: LIKE '%abc'
• Stale stats → bad query plan

Run EXPLAIN before you guess.

Which one got you?

[Ayush @ayushdoesdev]

Exactly. Observability turns ‘we can roll back’ into ‘we’ll know we need to within minutes.’

One practical add we use: pair the 15-min check with a canary or feature flag so the blast radius stays small even if the alert is imperfect.

Makes the two-way door actually two-way. Great thread.

[Ayush @ayushdoesdev]

AI code review can turn into a slot machine.

Pull → new nitpicks. Pull again → more.

What keeps it sane:
• Define "done" upfront: tests pass
• Fix only critical findings
• Review with a different model than the author
• Cap it at 3 rounds

What's your stop rule?

[Ayush @ayushdoesdev]

@iamvishal16_ios Glad that resonates, untracked files are the exact case I built it for.

If you try it, a ⭐ and any feedback on the repo would help a lot while it's still early:

https://t.co/kzYqZxAFsU

[Ayush @ayushdoesdev]

1/
AI coding agents are great, until one runs rm -rf on files git doesn't track.

So I built unwreck: Ctrl+Z for AI coding agents 🦀

unwreck undo and everything's back.

Open source, single Rust binary.
https://t.co/kzYqZxAFsU

[Ayush @ayushdoesdev]

PM: why is signup so slow?

Me: we send the welcome email, resize the avatar, and sync the CRM before responding

PM: and?

Me: moved it all to a queue. Respond first, work later.

PM: so you just... procrastinate?

Me: we call it async architecture 💀

[Ayush @ayushdoesdev]

@shade_ofc Cool… actually owning the invalidation problem instead of just documenting it.

How does the auto-caching + partition scoping decide what to invalidate on a write, and can you still force a fresh read when you need it?

[Ayush @ayushdoesdev]

Me: API is slow, let's add a cache

Week 1: responses are instant 🚀

Week 2: "why does my profile still show my old name?"

Week 3: me writing cache invalidation logic at 2 AM

There are only two hard things in CS and I'm failing both at once 😭

[Ayush @ayushdoesdev]

“Love the sticky-note framing. One small upgrade we’ve been testing: after the ‘pain + rollback’ check, ask ‘How will we know it broke within 15 minutes?’ If the answer is weak (no metrics, alerts, or easy verification), treat even a two-way door as a one-way until observability is added. Keeps the speed while reducing silent failures.”

This builds directly on the two-way/one-way idea without contradicting it, adds a practical filter most teams overlook with AI PRs, and stays concise and positive.

[Ayush @ayushdoesdev]

The failing test gate is solid. One upgrade that works even better for me: force the model to first output the exact sequence of side effects (payment captured → DB timeout → webhook redelivery) as a numbered list before any code, then generate the test that asserts the desired end state after recovery. If the list has any ambiguity, the test is useless.