$ cd ./villard

Just freshening up my pinned post to let you know I still maintain this account out of necessity to park my username and boost the signal of others via retweets and blogs. If you're interested in my regularly scheduled nonsense, you can find me on BlueSky charlesvillard.co/blog/what-envi…

Not everyone needs JARVIS, despite how useful such an idea may seem. Pretending the average person will want to go out of their way to ensure it will fulfill their needs is, effectively, coping with the strong possibility that it's just another flash in the investment hype pan.

And, no, modern LLMs aren't generating holograms yet, but that's not the issue. Everyone throwing hype at average people to convince them all the investment in a handful of companies, to be able to see some graphs you describe show up on a webpage, is worth it - that's the issue.

The "Search for JARVIS" is making people weird. Considering only ~0.6% of 168m US laborers design the aesthetic, physical, or tactile aspects of products for a living, the reply-guys saying the average user should want their agent to build what they want for them is laughable..

All my new code will be closed-source from now on. I've contributed millions of lines of carefully written OSS code over the past decade, spent thousands of hours helping other people. If you want to use my libraries (1M+ downloads/month) in the future, you have to pay. I made good money funneling people through my OSS and being recognized as expert in several fields. This was entirely based on HUMANS knowing and seeing me by USING and INTERACTING with my code. No humans will ever read my docs again when coding agents do it in seconds. Nobody will even know it's me who built it. Look at Tailwind: 75 million downloads/month, more popular than ever, revenue down 80%, docs traffic down 40%, 75% of engineering team laid off. Someone submitted a PR to add LLM-optimized docs and Wathan had to decline - optimizing for agents accelerates his business's death. He's being asked to build the infrastructure for his own obsolescence. Two of the most common OSS business models: - Open Core: Give away the library, sell premium once you reach critical mass (Tailwind UI, Prisma Accelerate, Supabase Cloud...) - Expertise Moat: Be THE expert in your library - consulting gigs, speaking, higher salary Tailwind just proved the first one is dying. Agents bypass the documentation funnel. They don't see your premium tier. Every project relying on docs-to-premium conversion will face the same pressure: Prisma, Drizzle, MikroORM, Strapi, and many more. The core insight: OSS monetization was always about attention. Human eyeballs on your docs, brand, expertise. That attention has literally moved into attention layers. Your docs trained the models that now make visiting you unnecessary. Human attention paid. Artificial attention doesn't. Some OSS will keep going - wealthy devs doing it for fun or education. That's not a system, that's charity. Most popular OSS runs on economic incentives. Destroy them, they stop playing. Why go closed-source? When the monetization funnel is broken, you move payment to the only point that still exists: access. OSS gave away access hoping to monetize attention downstream. Agents broke downstream. Closed-source gates access directly. The final irony: OSS trained the models now killing it. We built our own replacement. My prediction: a new marketplace emerges, built for agents. Want your agent to use Tailwind? Prisma? Pay per access. Libraries become APIs with meters. The old model: free code -> human attention -> monetization. The new model: pay at the gate or your agent doesn't get in.

Or your sham department was banned because you most likely violated their ToS. I bet you either overused their free offerings instead of paying them as a government entity, or you prompted it inappropriately to bias cutting programs you disagree with. Either way, glad they did.

Some part of me feels like naming hot startup companies 🦄 "unicorns" was a mistake. It turned them into mythical creatures for VC to try and birth through horrific economic rituals. Should have just called them "rich little surprises" or something.

The latest episode of Leet Heat is out, and I'm in it! I can't thank @jlengstorf enough for letting me be a part of it! It was an absolute privilege and a pleasure. I wrote a bit about my experience if you want a peek behind the scenes! charlesvillard.co/blog/leet-heat…

After getting both CSS and Animations as categories on Leet Heat, I feel personally victimized by design systems. Check it out to see if @cdvillard and I can handle the heat!!

This was a real nail-biter! @brittanyellich gave a run for my money, @marktechson wasn't having my antics, and @_anniebabannie_ was heavy with that spice! Check out how close the score was on this episode of #LeetHeat!

new Leet Heat! @brittanyellich and @cdvillard do their very best to survive the heat (and @marktechson's jokes) watch now! youtube.com/watch?v=ZY3uQb…

Posted on the OpenAI forum about using @pomerium_io to secure remote MCP servers with Zero Trust. It’s OSS, shows how to expose servers (e.g., GitHub or Notion) to LLMs without leaking tokens or redoing OAuth. Open to podcast invites or coffee chats! community.openai.com/t/zero-trust-a…

@WFLA View of the Alafia State Park fire from South Fork East. Feel free to use it.

Thanks everyone for checking out my talk at @vueconfus today! You can see some of my slides at slides.com/charlesvillard…!

Up next, @cdvillard takes to the stage with his session: Full-circle: a time traveler's perspective on Vue 🙌 #Vueconfus #vue #vuejs #Tampa

Take part in @cdvillard's session at VUECONF US this May, to explore the evolution of the framework and ecosystem through the eyes of a dev returning after a long break 🚀 vueconf.us/session?sessio… 🎟️ vueconf.us 🤩 Use code X100OFF for discount! 📅 May 19-21, Tampa

@joelhooks At least go to La Carreta, Sergio's was never the spot, imo.

@cdvillard look how many they make practice makes perfect

took all week but finally scored a cuban sandwich

I can't not complain about @indeed anymore. Search turns double quotes into unicode, listings don't include dates showing when jobs were posted, and results keep promoting the same roles Indeed thinks you want instead of just showing all actual matches. I can't with this!