Muhammad Ahsan Ayaz 🦋 @codewithahsan.bsky.social

I built a Pomodoro timer for streamers because I was tired of alt-tabbing during my coding streams. 60 seconds to set up. No plugins. No downloads. Here's how it works 🧵

May Allah give our Muslim brother shifa-e-kaamila! He has been doing incredible work in the past years.

Always having a backup plan! ✌️

Connect Gemini CLI to GitHub seamlessly! Learn how to set up Model Context Protocol (MCP) with a Personal Access Token to fetch your repos directly. Stop prompt stuffing, start fetching context. #Gemini

PR: github.com/TryGhost/Ghost… Self-host Ghost + use Resend? Pull my fork, kick the tires, leave a 👍 on the PR. Maintainer signal helps. Repo: github.com/AhsanAyaz/Ghost Blog: blog.codewithahsan.dev

What it doesn't do yet: - No webhook receiver (Ghost polls Mailgun; Resend pushes ... follow-up) - No per-send click/open toggles (Resend tracks dashboard-side) - No scheduled send (no Resend API for it) All called out in the PR body.

@Ghost only sends newsletters via @Mail_Gun . I wanted @resend . So I forked it and opened a PR upstream. 🧵 why + how

Getting feedback on projects can't be simpler than this. Loupe now supports "auto-pushing" loupe issues to @github repos and @linear projects. So if you're using Loupe's Web-SDK (takes <5 minutes to set up), you have this beautiful "Feedback" button on your web app, using which, your customers can send feedback about your projects. Be it a bug or a feature request. Something that broke, or could have a better UI, your users can take a screenshot, annotate on top of it, and send it right away to your GitHub and Linear projects. Try loupe for free. Sign up, create a project, link it with your GitHub repo using OAuth, and install the web sdk in your web app. That's it! Which platforms would you want to see integrated with Loupe? Do share in the comments. loupe.ink

I gave a TEDx talk today and it broke every rule I have ever set for myself on stage. My talks usually have a lot of slides. Technical diagrams. Code. Memes. Jokes. I navigate. I demo. I lean on the visuals. This one had 12 slides. Almost no code. No memes. No jokes that landed before minute four. No slides talking about myself, no achievements shown, no huge numbers. And then I walked on stage and discovered there was no second screen for my speaker notes. For 20+ minutes I paced. I talked. I tried to remember a script I had written and rewritten for weeks. And I tried to make sure the one thing I came to KTH to say actually got through. When the Q&A started, the students asked the questions I had been quietly hoping someone would ask. The thing I wanted to convey... actually got conveyed. The typing has been automated. The thinking has not. Thank you, @TEDxKTH Salon. 🌹 PS: It was awesome meeting @majabosni discussing what we like and don't like about Sweden, and getting a push for not using any cue cards during the talk. And I enjoyed @AnnaNorelius 's talk of why ideas don't land when pitched. And as someone who has built dozens of useful apps not reaching even a hundred users, I made sure to understand how to land them well. PSPS: Still waiting for official pictures. Will share once I have them. PSPSPS: Thank you Alex Hagdahl for inviting me for the talk, and for the nice bouquet. Which I enjoyed through my commute to home. And which I could give to my wife on reaching home. W! For those of you who did attend the talk at KTH Royal Institute of Technology today, I do plan to organize a bunch of Hands-On, AI workshops in Stockholm. Let's connect and make it happen. cc: @KTHAISociety

@AnasFirdousi Haha 🤣

2000s: I'm building B2C 2010s: I'm building B2B 2026: I'm building B2C2A2A2A User asks their agent. Their agent asks our agent. Our agent asks another agent. A human gets CC'd for vibes.

AI is changing software development, but what does it mean for junior developers? While AI boosts senior productivity, juniors still need to code manually, read books, and take courses. Understand *how* AI works, don't just prompt it.

Here's the guide: blog.codewithahsan.dev/build-smarter-…

The truth about long-term developer skills: there's no single magic bullet. Instead, focus on compounding skills and cultivating an adaptable mindset. Every learned framework or AI tool adds to your stack, so build it intentionally.

Opus 4.6 lately

"I don't understand. How is this AI Agent worth showing at Next?" This one caught my attention :) Here's the thing nobody tells you about visibility... I was reached out by @Google to share one of the AI Agents I'm working with at Google Cloud Next (happening in two weeks). I was not being invited to speak at Next because I built something extraordinary. I'm being invited because I kept showing up. Every "small" AI agent I shipped and shared. Every "basic" tool I documented publicly. Every project that someone might have thought or said wasn't impressive enough. All of it compounded. The person who asked that question probably has a brilliant project they're waiting to share. Waiting until it's polished. Waiting until it does something "extraordinary.". And perhaps would keep waiting until the tech becomes outdated, or someone else ships a simpler version that people start using immediately. Meanwhile, the invite goes to the person who shipped the imperfect one. Here's what I've learned after years of building in public: - Nobody discovers you from the one big thing. They discover you from the tenth small thing. - The extraordinary project you're waiting for? It comes after you've shipped the "not good enough" ones. So stop waiting. Build the thing. Share the thing. Repeat. The stage finds the consistent ones. Not the perfect ones. ♻️ Repost if this hit home. Someone in your network is waiting for permission to ship.

Join a hands-on Build with AI workshop this Saturday! Learn to build a travel agent using Gemini CLI. Limited spots available. Register now for Google Cloud credits! forms.gle/jM8mt2UhHFbek4…

If you're vibe coding and feeling like a fraud, like you're not "really" coding anymore... You're not alone. The shift from writing every line → directing AI is real. It's not laziness. It's leverage. The best architects don't lay every brick. They design the building. I feel like that's our new job. Probably time to own it.