Mostafa Said

If I’ve learned anything about programming over the years, it’s to be suspicious of any person who repeatedly evangelizes increasingly complex approaches and techniques.

Watch @alexdotgs vibe code a fitness tracking app, twice. Once with no planning, then again with 5-10 minutes upfront time on a spec. The difference is clear 💪

I think I could help Anthropic Mythos fix opus, no mistakes

@evanyou @theo Yes Claude sucks recently, you’re not alone

Honestly don't know what happened to Claude Code. Tried a one-off simple task on a fresh directory yesterday, tried a bunch of things that didn't work, asked for a ton of permissions, and then got stuck for 4 minutes before I got tired of waiting and killed the session. This was on medium effort. Switched to Codex gpt 5.4 with medium effort and one shotted the task in under 1 minute.

Just got done shooting a course all about Vite+ (so stay tuned in the next couple weeks for that on @VueSchool_io !) But shameless promo aside, honest question 👇 What should I teach a course about next? What's exciting you around #vuejs, #nuxt, or #webdev?

Very soon, being a good developer is going to be one of the most valuable skills out there. Lazy AI habits will flood the market with average work, and that’s exactly why good developers will be needed more than ever ever. It won’t be easy to get hired because all of the noise, and companies won’t find you easily either. But when they do, they’ll pay.

@mattpocockuk But you get to control the plan 🤔

I have also stopped using plan mode It creates a plan FAR too eagerly and usually asks you zero questions en route The whole point of planning is to get on the same wavelength with the LLM, not to generate an asset you don't read /grill-me all the way

I could play with this all day long! x.com/thedorbrothers…

AI happened. There's no way around it, only through it.

@jpschroeder Congrats to the React ecosystem on this gem👑

Hell froze over: announcing FormKit for React. Secretly framework-agnostic since inception, today we’re open sourcing the most popular Vue form library…for React. Why is this a big deal? 1. Forms are still hard. We (the creators of FormKit) thought form libraries were no longer necessary, given the trajectory of coding agents. It turns out we were wrong, and we learned this the hard way. Need repeating conditional fields nested 3 layers deep inside a dynamic component, with accessibility, validation, internationalization, and backend error placement? Turns out coding agents aren’t great at that. It’s table stakes for FormKit. 2. Single component. This matters more than you would think, but FormKit doesn’t ship lots of different components each with its own props. Instead, it has a single one: and unified props. This was done to provide a better DX to human engineers. It makes it easy to spot when a given component was part of the form’s data structure vs a presentational component. It turns out this matters even more to coding agents than humans. No matter where your coding agent is, whenever it sees “FormKit” it immediately knows “oh, that’s part of the form’s data”. 3. No plumbing. FormKit doesn’t require any manual data collection, event listening, or state tracking. It does all this for you on a heavily tested, framework agnostic, self-assembling graph. The only code your agent needs to write is declarative templates and submission handlers that respond to the state. 4. Dense colocation. FormKit’s syntax happens to be ideal for coding agents; nearly everything you need to know about a given input is *on* the input: Colocation dramatically improves the efficacy of coding agents. 5. DOM. FormKit, unlike most form frameworks in React, renders the actual DOM. This also increases colocation and best practices, meaning your coding agent is far more likely to produce consistent and high-quality output that looks and acts the way its supposed to. 6. Schema. FormKit’s own inputs are not written using Vue or React — instead, FormKit has its own render schema — think of it like an AST for the DOM — and you can modify it on the fly. It’s not very human-friendly to write, but it turns out most models are already pretty well trained on FormKit’s schema. Want your inputs to look a bit different on one form than another? No problem, your coding agent can easily make those changes *without* modifying the JSX structure at all. Oh, and any inputs you create for Vue work with React and vice versa. 7. Plugins. FormKit leans into the unstructured tree graph hard. The graph doesn’t just collect data, it also passes down configuration and plugins. Want one form to work a bit differently than another one? No problem — just add a plugin to the top of that form or group and its children will all receive that feature. You can even mass assign props and configuration this way. Of course, FormKit has been solving these exact issues for a long time, but it wasn’t until we started using it on our own projects with coding agents that we realized what a huge advantage it is. With so many people using coding agents with React, it made sense to unveil FormKit for what it has always been — a completely framework-agnostic form framework that happens to unlock your coding agents. ➡️ formkit.com

@posva @vercel @nuxt_js Congrats!!

I’m joining @vercel and the @nuxt_js team! Excited for the times ahead and really grateful for this opportunity!

One of the hardest things to do in life is "unlearn" old habits and skills... But the world doesn't stay still and we can't either. Time for some un-learning 💪👇

Early Access is now LIVE! 🚀 Only 500 seats, 48 hours - that’s it. Unlearn your old habits and master the workflows, decisions, and planning that actually make software work. Think you’re ready? Get access 👇 go.unlearn.dev/ea126x

Don’t miss early access. Absolutely amazing value for what we’re about to give you.

So proud of this one unlearn.dev 🔥 @UnlearnDev

The process behind building your own skills in @claudeai (and it’s not hard). Watch @alexdotgs build a code review skill that delegates to any agent and reviews any part of your codebase.

Can you relate to this awkward tension I feel of being endlessly excited by what AI now unlocks (you can build anything you want), but with this constant underscore of depression that I can't explain?

The way developers work has changed, and with it comes more confusion than ever. How do you keep up, stay truly productive, and continue to build quality software? Excited to share what we've been working on: unlearn.dev