I much prefer this future prediction over the "AI is gonna steal all our jobs" one. Let's go!

MCP is the future. Most software will be AI-native soon—and this is how it happens.

Does AI change the conversation about the “best” front-end framework? On one hand, AI tools seem to work better with the most widely-used frameworks (React, Angular...)— because that’s what they’re trained on, and that’s what shows up in the prompts. Popularity boosts AI

To toast or not to toast? 🍞 Talked about that in a meeting at work today, and well... there’s lots of opinions on it. UI toasts can be great for quick, non-blocking feedback—but they’re also easy to miss and often misused for important messages. So what’s the right way to

Because of MCPs, I believe the web/mobile experience as we know it will disappear—and quickly. We’re moving beyond screens and clicks into a world of seamless, multimodal, conversational interfaces.

Build people. Build code. And the order matters. The best engineers I’ve worked with don’t just ship features—they uplift others, mentor, and invest in the culture around them. Strong teams build strong software, but they also build each other in the process.

Preparing a talk for an upcoming Remix meetup in 2 weeks. At first, I had a technical topic lined up — but the more I thought about what would be most impactful, I kept coming back to themes like career growth, impact, and making a difference. Curious: what are your thoughts on

Happy Easter 💕 #HeIsRisen

Hoping for a future where AI helps us create better, not just more. Right now, 8 out of 10 posts feel like low-effort, high-volume noise—even from people I used to love followin

Engineers often get stuck in the thick of thin things—myself included. I’ve been learning, over and over again, that clarity of outcome beats complexity of input every time.

AI Clients are the new browser MCP Servers are the new websites

Come hang out with me at the Remix Meetup this Thursday in Lehi! In a world shaped by AI and nonstop change, technologies fade — but great engineers leave a legacy so I’ll be sharing a few thoughts on how to go beyond the code and build a career worth remembering. Come network

I honestly believe there are two kinds of people: Consumers and Creators. We all play both roles in different aspects of life—but I'm convinced only creating brings true fulfillment. So create. Contribute to that open source project. Share what you’ve learned. Write the app

Just got accepted to speak at my first conference… and now I’m thinking: what did I just get myself into? 😅

Struggling to balance building with GenAI (using it as a tool) vs. building AI-native tools (like creating MCPs), all while maintaining and shipping features on the current web stack. What’s the right mix?

Pair programming is criminally underrated. I spent half the day pairing with an engineer on my team—we moved faster, solved tougher problems, and both walked away sharper. It’s one of the fastest ways to level up engineers and ship better software, both in the short and long

Fail cheap. Fail fast. That’s been a personal moto for years.

Sunday is the kind of day that reminds me why I work hard the rest of the week—it’s a chance to spend my time intentionally and refocus on what matters most.

I’ve had the awesome opportunity over the last couple of weeks to talk with developers who are still in school, as well as others actively looking for jobs — and I’ve noticed a clear trend, especially with the rise of AI: Companies aren’t necessarily hiring more engineers — but

Caching is hard. I wish someone explained it like this years ago. So I did now— for anyone who needs it. No fluff. Just code. Cache me if you can :) wargha.com/blog/cache-me-…