(From the Complete Beginner’s Guide to Vibe Coding an App in 5 Minutes, 9 Ⅹ 25)James Montemagno (Microsoft) wrote:The Future is Vibes
This isn’t the future—it’s now. GitHub Copilot with advanced reasoning models like Sonnet 4.5 has fundamentally changed how we build software. The question isn’t “Can AI write code?” (yes, obviously). The question is: “How do I collaborate with GitHub Copilot to build better software faster?” Here’s my framework:
- You own the vision – What are we building and why?
- Copilot owns the implementation – How do we build it?
- You own the quality – Does this actually work?
- Together you own the outcome – Did we solve the problem?
(From the Google Cloud help files, 2025)Google wrote:Vibe coding [as these firms call this practise] is more than just a new technique. It’s helping shift how we create software. It lowers the barrier to entry for new creators and acts as a powerful force multiplier for experienced developers, allowing everyone to focus more on creative problem-solving and less on manual implementation.
I do not know how much the Pale Moon development team has been forced to deal with such blindly synthesised code appearing in Mozilla updates thus far, but I suspect that it might soon appear more often if it has not already. Malformed Windows 10/11 updates are nothing new, of course, but I cannot help but wonder whether some of the most recent could have been caused by this also. Beyond the obvious effects, this practise is more interesting to me because, as only open-source software can meaningfully be scraped, it strips away the usual problems about privacy, copyright* and aesthetics which surround discussion of LLM and related syntheses, letting the technology be judged solely on its own merits. It is telling that, even under these most favourable conditions for it, it proves just as terrible a blight.
*I realise that precise compatibility with (eg) attribution or the GPL might be neglected, but this does not alter the point.
