Mian Shahzad Raza

@TTrimoreau Just lunched on the product today, and it doesn't feel worth it anymore.

Is Product Hunt still worth launching on?

@gitlawb I tried, it does not work. Package not found

We forked the leaked Claude Code source and made it work with ANY LLM: GPT, DeepSeek, Gemini, Llama, MiniMax. Open source. The name is OpenCode

@GithubProjects Great open source strategy. Just accidentally leak 512K lines via npm. Very intentional. Very bold. 10/10 Anthropic.

> Thanks Anthropic, for Open-sourcing claude code.

@steveruizok Jumped into this stack from WordPress and never looked back. Next.js pages router was so clean it made the app router feel like a downgrade at first. Still feels that way sometimes.

there was a moment in 2023 when your team was using Figma, Linear, VS Code, Typescript, React 18, esbuild or Next.js with the pages router. Peak software in every category. wonderful stack. you were young and happy and in love

@CodeEdison Missing from the backend list: headless WordPress + WPGraphQL. Pair it with Next.js and you get serious content flexibility without the full rewrite. Especially powerful when clients are already on WP. Same data layer, way better DX.

Full-Stack Developer’s 2026 Tech Stack • Frontend → React / Next.js / Vue.js • Backend → Go / Rust / Spring Boot / Node.js / Django • Database → PostgreSQL / MySQL / MongoDB • Authentication → JWT + Refresh Tokens / OAuth 2.0 • Infrastructure → Docker + Kubernetes / Nginx as Reverse Proxy • CI/CD → GitHub Actions / GitLab CI / Jenkins • Additional Tools → Redis (Caching), Kafka (Event Streaming), GraphQL (APIs)

@averycode The 'explicit constraints' tip is underrated. Coming from WordPress dev, I learned this the hard way: vague prompts = spaghetti code. Now with React I treat the AI like a smart junior: clear spec in, review out. The discipline makes vibe coding actually ship-able.

3 days ago, I vibe coded a game and it went viral Can’t believe 350k+ people watched me try to beat my high score 😮‍💨 Here are my vibe coding tips for mobile apps: > Build using opus 4.5 on rork ai > Start with a clear, well defined goal > Be explicit about constraints (8x8 grid, block shapes and sizes) > Define the game loop step by step - instead of “build a block blast clone” > Refine the prompt on chatgpt first to save credits (Full prompt in replies)

@leerob Shadcn + Tailwind is exactly where I landed too — coming from years of WordPress theme dev. Server Components flipped my mental model: stopped thinking "where does this fetch?" and started thinking "what layer owns this data?" Clean architecture win.

Here's how I usually structure my Next/React apps. Let's talk about styling, data fetching, UI libraries, settings, and more. Styling The short story is Tailwind. Why? It was easy for me to pick up, stays consistent whenever I revisit old projects, and works great with AI / @v0. I've wrote a lot more about this here: leerob.io/blog/css Data Fetching For those who have been around Next.js for a while, you know the quirks of the Pages Router. No end-to-end type safety? No global data fetching?? The App Router is so much nicer in this regard. So, I've been defaulting to this for almost two years now (time flies...): #end-to-end-type-safety" target="_blank" rel="nofollow noopener">nextjs.org/docs/app/build… Most of the time, I fetch data in a Server Component (like a page or layout). Occasionally, I'll still pull for an external lib for client-fetches (e.g. swr) when working with existing codebases. A newer pattern that I've started to sometimes use is forwarding Promises to a Context provider, and then "unwrapping" the Promise with `use`. The data can then be used from a hook in any client component. Can work well if you have global data you need to use deep in the component tree (esp. if there's lots of client components): #L148-L155" target="_blank" rel="nofollow noopener">github.com/vercel/commerc… UI Libraries Can I say something without everyone getting mad? I wasn't really a fan of shadcn/ui at first. It felt like a lot of dependencies and "weight" in my repo. There was something more minimalist about just putting the deps in `package.json`. It was similar to my initial reaction to Tailwind. "Eww". Well, that was wrong too. Maybe that was just my familiarity with existing component libraries. I've really changed my opinion. Unstyled, accessible UI components that integrate with Tailwind are... really nice. And that can be easily edited and customized. You either use a component library, or you build your own. And there's so many dang quirks to get accessible components right. I think that's why unstyled primitives are growing so quickly. It's really a new generation of component libraries. Other Libraries I almost never use ESLint on personal projects anymore. I still use it when working on larger projects with the team. But type checking + Prettier has been good enough. Long live TypeScript. We're hoping to add support for Biome to Next.js, and then maybe having the single unified toolchain will be my new approach. Not sure yet. Prettier has worked so well, for so long, I'm apprehensive to any change. cc: JS fatigue. In general, I'm trying to have fewer dependencies, because you can often get an AI-assisted version of just the one function you needed versus bringing in the whole package. Things like date formatting, or markdown parsing. I wrote more about this here: leerob.io/blog/2023 • An extremely underrated Postgres client is `postgres.js`: github.com/porsager/postg…. However, most of the time I'm using `drizzle` as my ORM. • `zod` somehow finds its way into almost all of my projects these types. Forms You can get surprisingly far with the new React hooks like `useActionState` and Server Actions. Throw some Zod in there, and it's pretty easy to get client/server-side validation with ease: github.com/vercel/next.js… There's a few community packages automatically setting this up for you, which is nice: next-safe-action.dev Charts shadcn/ui: x.com/shadcn/status/… Icons shadcn/ui, so `lucide-react` currently: lucide.dev/icons/ Fonts Geist: vercel.com/font Settings I daily drive VS Code. I do want to learn neovim at some point, btw. I don't have any fancy extensions, mostly just the essentials: Tailwind, Prettier, MDX, vscode-icons. Maybe will try Zed again when the git support improves: x.com/leeerob/status…. Or maybe some of the new AI enhanced editors (I do use Copilot currently). A few VS Code settings you might have that I like: "editor.cursorSmoothCaretAnimation": "on", "editor.smoothScrolling": true, "editor.cursorBlinking": "solid", I'd also recommend checking out custom editor labels if you hate the page/layout/route duplication: x.com/nextjs/status/… Payments Stripe It was easy for me to pick up, stays consistent whenever I revisit old projects, and works great with AI / @v0. Iterating I spend a decent amount of time now talking to @v0 to help make edits or debug things. Definitely not perfect, and it gets things wrong sometimes, but saves me a lot of time versus writing everything from scratch. Especially for more tedious refactors that are basically just pushing code into different places, or reformatting/restructuring it. You can kind of 'fire and forget' @v0, then do something else, return in 15 seconds or so, copy the output, and keep moving. It's like my concurrency level went from 1 to 2. AI agent workflows might make this even easier in the future. Summary "Well, you know, that's just like uh, your opinion, man."

@jeremykoering People said a lot of thing about AI can't do, its doing it now.

@MSR_Builds People said that last year. And the year before. The miscalculation is that uncreative people assume AI is creative, which it is not.

Social media feeds me the same trash AI takes every day. "WordPress is dead, AI killed it." Blah blah blah. I'm convinced AI is a shell game. AI cannot create on its own. It can only steal and regurgitate a human's work. It is not creative. It can only create what you imagine. The best output requires knowledge, expertise, and skill. If someone says something like "AI has killed WordPress," I would question whether that person should be listened to.

@theo I am glad by the time I reached Tailwind (coming from WP ecosystem with Bootstrap) I didn’t have to memorize class names 😂

Can’t believe I spent years learning all the Tailwind class names just to have AI write them for me

@melvynx Coming from WordPress dev → React, this hit different. WP taught me to name things (hero, card, sidebar). React just made the vocab sharper. Knowing component terms before you prompt = cleaner AI output every time. 🎯

Pro tip for Vibe Coding: just knowing the "terms" behind UI components can 100x your frontend results This website shows you ALL the typical UI components found on websites with examples and inspiration Learn it, screenshot it, and vibe code

@trikcode The crash hits those with no debugging foundation. My WordPress background (PHP hooks, plugin conflicts, theme quirks) forced me to understand what's actually running. Now I vibe code React the same way — always ready to read the mess the AI made. 🔍

The vibe coding crash is coming. Thousands of apps built by people who can't explain a single line of their own codebase.

@karpathy As a WP dev who started vibe coding my way into React — this throwaway tweet gave me the permission slip I didn't know I needed. A year later I'm shipping full-stack apps faster than I ever could with a decade of WordPress behind me. Unpredictable impact, for real. 🙌

A lot of people quote tweeted this as 1 year anniversary of vibe coding. Some retrospective - I've had a Twitter account for 17 years now (omg) and I still can't predict my tweet engagement basically at all. This was a shower of thoughts throwaway tweet that I just fired off without thinking but somehow it minted a fitting name at the right moment for something that a lot of people were feeling at the same time, so here we are: vibe coding is now mentioned on my Wikipedia as a major memetic "contribution" and even its article is longer. lol The one thing I'd add is that at the time, LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and explorations. It was good fun and it almost worked. Today (1 year later), programming via LLM agents is increasingly becoming a default workflow for professionals, except with more oversight and scrutiny. The goal is to claim the leverage from the use of agents but without any compromise on the quality of the software. Many people have tried to come up with a better name for this to differentiate it from vibe coding, personally my current favorite "agentic engineering": - "agentic" because the new default is that you are not writing the code directly 99% of the time, you are orchestrating agents who do and acting as oversight. - "engineering" to emphasize that there is an art & science and expertise to it. It's something you can learn and become better at, with its own depth of a different kind. In 2026, we're likely to see continued improvements on both the model layer and the new agent layer. I feel excited about the product of the two and another year of progress.

Here is my workflow: I build for myself, then add more features and ship it for others. An example: wplauncher.msrbuilds.com I started with a tool to help me distribute my plugins/themes so the users can test them in a sandbox environment. Later on, it turned out to be a fully functional local development toolkit (that replaced Laragon/LocalWP) for me and an online platform where anyone can distribute their products OR launch WP instances for clients on a VPS.

Are you using what you're building? I dont think this line its always accurate, especially for us builders

@boxmining Hi

Everyone who loves: - AI Automation - AI Agents - Vibe Coding - Crypto / Stocks investing - Content Creation - Saas / Start-ups - Financial Freedom I hope you find my account 👇🏼

@phuctm97 I don't think so. AI agents can just use search and browse now.

Is Context7 MCP still necessary these days?

@vivoplt The $20 pack is outdated now. You need at least $100 to build something solid.

The vibe coding stack in 2026: Claude: $20/mo Supabase: $0 Vercel: $0 GitHub: $0 Domain: $10/yr You don't need a CS degree. You don't need a co-founder. You need an idea and a weekend. Ship it.

@bcherny One I'd add: `/init` to generate a CLAUDE.md for your repo. Game changer for WP+React projects — I store all my hooks, CPT names, and ACF field schemas there. Claude stays in context across sessions without re-explaining the architecture every time.

I wanted to share a bunch of my favorite hidden and under-utilized features in Claude Code. I'll focus on the ones I use the most. Here goes.