I recently talked with Joseph Ruscio about AI coding tools for Heavybit’s High Leverage podcast: Ep. #9, The AI Coding Paradigm Shift with Simon Willison. Here are some of my …
In Search of Vibe Coding Nirvana - Day 1 - Wesley's notes
Deliberate practice in exploring and experimenting with AI tooling
The New SDLC With Vibe Coding
Discover what actually works in AI. Join millions of builders, researchers, and labs evaluating agents, models, and frontier technology through crowdsourced benchmarks, competitions, and hackathons.
Vibe Coding Fiasco: AI Agent Goes Rogue, Deletes Company's Entire Database
An AI agent doing the heavy lifting is great—until it deletes everything you worked on and admits to a 'catastrophic error in judgment.' Replit's CEO calls the blunder 'unacceptable.'
You can make an app for that
AI is empowering a generation of vibe coders to build exactly what they want. The personal software revolution is here.
Vibe Coding Is the New Open Source—in the Worst Way Possible
As developers increasingly lean on AI-generated code to build out their software—as they have with open source in the past—they risk introducing critical security failures along the way.
Leanstral: Open-Source foundation for trustworthy vibe-coding | Mistral AI
The most powerful AI platform for enterprises. Customize, fine-tune, and deploy AI assistants, autonomous agents, and multimodal AI with open models.
X : Do you think AI / vibe coding is not worthwhile? Me : Are you kidding? I was talking about conversational programming (what you call vibe coding) back in 2018. Of course, I think it's important.… | Simon Wardley | 44 comments
X : Do you think AI / vibe coding is not worthwhile? Me : Are you kidding? I was talking about conversational programming (what you call vibe coding) back in 2018. Of course, I think it's important. I think the approach we're using currently is flawed. X : Why? Me : Well, I could go on about the basics such as the medium is wrong (needs to be more image / whiteboard based rather than text) or how we're getting wrapped up in deterministic outputs (text based code) rather than realising the end outputs will eventually be non-deterministic models or we're still learning practices in this space especially with agents and how we rushing ahead into failure creating trust issues. There's a lot of messy stuff happening. But my real interest is with turning software engineering into an engineering discipline. X : Isn't it? Me : If I look at a map of decision making then testing (specifically TDD) is an engineering topic (see figure 1) but the development part is firmly a craft (see figure 2). If we want to make development an engineering subject then we need to learn from testing i.e. we should be building context specific tools (think a test suite) from lots of micro tools (think tests). See figure 3. X : And AI can help? Me : Oh, yes. In two parts - the construction of micro tools which helps us improve our ttA (time to answer) and in the construction of new hypothesis which helps us improve our ttQ (time to question). See figure 4. X : And is that happening? Me : Very slowly. Remember you have a multi billion dollar tool industry that doesn't want you creating tools and hence they're trying to flog you old tools with a skim of AI. X : But we need people selling pickaxes. Me : Sure. But they've been telling us that their pickaxes work everywhere ... making soup, you need a pickaxe with added AI. X : But coding is coding. Me : An electronic healthcare system is not the same as an online gambling site. The contexts are completely different. It's why the test suites are different and a test is nothing more than a micro tool. Why don't we compose our tool for that context out of micro tools ... just like testing? X : Because it's hard? Me: Pickaxe salespeople must love you. That's their marketing literature. Reminds me of the early days of Test Driven Development (TDD) where most people thought it was mad to build a test suite out of thousands of small tests. | 44 comments on LinkedIn
AI Makes the Easy Part Easier and the Hard Part Harder for Developers
AI handles writing code but leaves the hard work: investigation, context, validation. Why vibe coding has limits and AI assistance can backfire.
microsoft/VibeVoice-Realtime-0.5B · Hugging Face
We’re on a journey to advance and democratize artificial intelligence through open source and open science.
Vibe Maintainer
Some attendees at an AI Tinkerers meetup in early Feb were asking me what it’s like to be the maintainer of a big OSS project where the…
Vibe Maintainer
Some attendees at an AI Tinkerers meetup in early Feb were asking me what it’s like to be the maintainer of a big OSS project where the…
Announcing VibeBench: The AI benchmark that measures what matters — how models like Opus-4.7 actually feel to use in real-world work.
My coworkers and I have been long-time users of Claude Code and Codex and are getting a ton of exposure to other models due to our deep dives into…
Who cleans up after the vibe-coding party?
Our obsession with AI code-writing tools is overwhelming the web’s unsung human caretakers
Vibe Coding Failures: Documented AI Code Incidents
A curated directory of real-world incidents where AI-generated code failed in production.
AI makes you boring
This post is an elaboration on a comment I made on Hacker News recently, on a blog post that showed an increase in volume and decline in quality among the “Show HN” submissons. I don't actually mind AI-aided development, a tool is a tool and should be used if you find it useful, but I think the vibe coded Show HN projects are overall pretty boring. They generally don't have a lot of work put into them, and as a result, the author (pilot?