You can just render images on the terminal btw:
▲ ~/ npx ai-cli image 'a vercel ai sdk diagram'
Run 𝚗𝚙𝚖 𝚒 -𝚐 𝚊𝚒-𝚌𝚕𝚒 and access every image, video & text model from @vercel AI Gateway instantly
Next.js 16.2 introduces a stable Adapter API, built with Netlify, Cloudflare, OpenNext, AWS, and Google Cloud. But the API is only part of the story.
Next.js is used by millions of developers across every major cloud, and making it work well everywhere is on us. Here are our commitments.
https://t.co/ylGpJG3WpZ
Introducing Design System Agents.
Turn your repos, npm packages and docs into an agent that builds prototypes engineering can actually ship.
The Prototype is t̶h̶r̶o̶w̶n̶ ̶a̶w̶a̶y̶ the Product.
Introducing the new @stitchbygoogle, Google’s vibe design platform that transforms natural language into high-fidelity designs in one seamless flow.
🎨Create with a smarter design agent: Describe a new business concept or app vision and see it take shape on an AI-native canvas.
⚡️ Iterate quickly: Stitch screens together into interactive prototypes and manage your brand with a portable design system.
🎤 Collaborate with voice: Use hands-free voice interactions to update layouts and explore new variations in real-time.
Try it now (Age 18+ only. Currently available in English and in countries where Gemini is supported.) → https://t.co/pmT9iHEpZa
جو لوگ اپنی پارٹی قربانیاں دینے والے ورکرز کی مرضی سے نہیں چلاتے وہ ملک عوام کی مرضی سے چلائیں گے؟
عوام راج تحریک ایک ایسی سیاسی جماعت بنائے گی جس کے ہر فیصلے میں عام ورکر شامل ہو گا، جس میں عام ورکر بھی منتخب ہو کر چیئرمین بن سکے گا۔
#AwwamRaaj
Our latest Claude Code hackathon is officially a wrap.
500 builders spent a week exploring what they could do with Opus 4.6 and Claude Code.
Meet the winners:
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.
There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.
@MrAhmadAwais Yes, because most of AI driven development now is conversational and IDE were designed to be based interaction. This is changing whole development paradigm.
We are excited to announce the arrival of our most requested adapter! 🚀
OpenRouter adapter lands in TanStack AI with over 300+ models for you to play with! 🔥
Try it out with the latest version today!
I hear a lot of junior developers are being discouraged from using ai coding agents by seniors who still think ai isn’t capable enough.
This is absolutely wrong.
There other reasons I hear often that juniors should build better understanding of systems instead of over relying on ai.
I couldn’t disagree more.
The first time i learned to write a for loop was actually by looking at that code. Watching it execute. And then way later understanding how it actually worked.
You learn more by building than by anything else.
For years I’d encourage junior devs to build ten projects a month.
You learn by building. By deploying real solutions to problems. Especially when a couple of people start using it. That’s where the learning begins.
I built a title case headline maker like 20 years ago to learn regex in JavaScript. That silly thing is used by journalists of many major publishers (i started recording events so i know).
And building real world projects used to be extremely hard for juniors. Often they’d give up mid way.
I have seen CS grads leave this field thinking they’re never going to be great programmers.
This has completely changed today.
Programming is not the bottleneck anymore.
You can build hundreds of silly projects in a week. Deploy and share them.
You should read the source code. And yes it’s fine to not know or not understand everything before you make it live for your side projects.
That’s how you learn. You now have the ability to front load years worth of mistakes & learning before you go build real production systems.
This is amazing for learning, for building portfolio, for deepening your understanding of how the tech stack works.
You can easily improve legacy systems. You toy around with different ideas and translate them into “I think it should be done this way” projects.
You should write a whole lot more code today. 10x more.
You should build new workflows that many senior engineers have not even thought about.
This is a crazy time for anyone who wants to learn fast and build great things.
Do NOT hold yourself back on the account of someone who’s never done it. (Many seniors have not done parallel coding of say five projects with five coding agent at the same time. The workflow is absolutely different than what any one of us was ever used to).
Go build.
Use your code for good.
Real Luxuries in Life
1. Living 10 minutes from work
2. Living 5 minutes from the gym
3. Having quiet neighbors
4. Having money left at the end of the month and investing it
5. Peace at home
6. Drinking coffee without rushing
7. Sleeping with a clear conscience
8. Laughing with people who truly get you
9. Traveling every year
10. Waking up naturally without an alarm
11. Enjoying a home-cooked meal with loved ones
12. Having time to read a book in one sitting
13. Finding joy in simple daily routines
14. Having a pet that greets you happily at the door
These are the things that actually feel rich.