Vibe coding is the future of MediaWiki extension development
| MediaWiki Users and Developers Conference Fall 2025 | |
|---|---|
| Vibe coding is the future of MediaWiki extension development | |
| Talk details | |
| Description: | Continuing my talk in May about vibe coding to show how new agent-mode tools like Cursor and Copilot transform AI-assisted coding, and why the MediaWiki community should adopt best practices for organizing extensions. |
| Speaker(s): | Jeffrey Wang |
| Type: | Talk |
| Audience: | Everyone |
| Event start: | 2025/10/29 15:50:00 |
| Event finish: | 2025/10/29 16:20:00 |
| Length: | 30 minutes |
| Video: | not available |
| Keywords: | AI, extensions, vibe coding |
| Give feedback | |
In May, during the MediaWiki Users and Developers "Workshop" in Sandusky, I alluded to the efficacy of vibe coding when there is a good structure provided to the vibe coding platform. Agent mode is a recent feature added to tools like Cursor and GitHub Copilot which is a game changer in AI-assisted coding. I now believe it would be beneficial to the third-party MediaWiki community to centralize on the best practices of how to organize a MediaWiki extension.
I believe it is time to normalize “hybrid” vibe coding as the primary form of coding going forward. When done right, vibe coding gives huge productivity boosts. There is simply no way a human can type as fast as an LLM.
The main problem with vibe coding now becomes not every third-party extension “imaginer” will know how to carry this out properly. That’s why I think the time is ripe to create a set of best practices, so even people not traditionally trained in software development but who have ideas may realize their dreams without creating vibe coded garbage. We should not dismiss vibe coding as a joke; it is very much becoming the norm to write most code with the help of LLMs and for software engineers to be the “overseer” and ultimate auditor of the code output.
