TL;DR You can integrate Azure DevOps with GitHub to get the best of both worlds in Power Platform development. ADO stays as the backbone: work items, sprint planning, test plans, and deploy pipelines all remain on Azure DevOps. Code moves to GitHub: Power App Code Apps or Power Pages SPA live in GitHub repos, unlocking native GitHub Copilot integration and the Copilot Cloud Agent. The two platfo
It started at midnight I had 24 hours, a free Replit subscription, and an idea: what if I could build something like Miro — but actually understand every line of code in it? The core problem I had to solve first Multiplayer sync sounds simple until you actually build it. The hard part isn't sending a canvas update — it's figuring out what to send. canvas.on('object:modified', (e) => { socket.emi
FutureMe has 15 million letters in its database. They've been there since 2002. Some of them will be there in 2050. Evengood will have zero. This week I shipped The Quiet Letter — a feature where you write to your future self today, we email it on a date you pick, and we hard-delete the row from our database within 24 hours of sending it. The email is the only artifact. We don't keep a copy. Every
GitHub Copilot just got a lot more complicated — and not in a good way. If you tried to sign up for Copilot Pro recently and hit a wall, that's not a bug. GitHub quietly paused new sign-ups for Copilot Pro, Pro+, and Student plans starting in late April 2026. No end date announced. No workaround offered. Just a message and a door that won't open. That alone would be worth covering. But they made t
Microsoft's 'Co-Authored-by Copilot' Tag: Unpacking the Strategic Play for AI Dominance in VS Code The persistent insertion of 'Co-Authored-by: Copilot' into commit messages within VS Code—often irrespective of GitHub Copilot's active contribution to specific changes—is far from a benign engineering detail. It represents a calculated, multi-faceted strategic maneuver by Microsoft, signaling a pr
It was around 1am and I had three feeds open. X on my phone, Reddit on one monitor, Hacker News on the other. I was reading about a plane crash, a new AI model, and a meme war about whether oat milk counts as milk. And I realised I had no idea what the internet was actually feeling about any of it. The feeds told me what was happening. They didn't tell me how it felt. That's when the idea hit me.
What if your code editor could do keyword research, audit your SEO, and optimize your content for AI search engines — without leaving VS Code? I built a set of open-source agent skills that turn GitHub Copilot into a hands-on marketing strategist. Here's what I learned, how they work, and how you can use (or build) your own. The problem Open Ahrefs/Semrush → research keywords What if I could encod
The grey enemy and the friend to save me from it If you're a software developer and you are on GitHub, you already know what I'm talking about: the contribution graph. That public heatmap on your profile that tracks your every commit, PR, and review you've ever made. That grid of gray and green squares that (in some cases looks like a well maintained patch of grass) tells a story about your codi