# Case study of an amateur plugin author

**URL:** https://meta.discourse.org/t/case-study-of-an-amateur-plugin-author/402084
**Category:** Development
**Created:** [3 במאי,‏ 2026,‏ 3:41am UTC](https://meta.discourse.org/t/case-study-of-an-amateur-plugin-author/402084 "2026-05-03T03:41:19Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![jericson](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jericson/32/116215_2.png) [@jericson](https://meta.discourse.org/u/jericson)
#### Post date: [4 במאי,‏ 2026,‏ 6:07am UTC](https://meta.discourse.org/t/case-study-of-an-amateur-plugin-author/402084/4 "2026-05-04T06:07:37Z")

</div>

> [@Moin](#):
>
> I think you got the error because of this bug, not because your plugin needed an update right now

Does seem likely. Getting on the latest ESR (and being a bit more vigilant testing) seems like a good plan from now on.

> [@piffy](#):
>
> I think with the advent of agentic coding, this development pace has become a non-problem.

I don’t think pace of development is a problem _per se_. It’s the pace of _everything_. Why hasn’t [the plugin tutorial](https://meta.discourse.org/t/developing-discourse-plugins-part-2-connect-to-a-plugin-outlet/31001) been updated for instance? It’s a mine waiting to blow up in the face of some poor sap who wants to build a plugin. It’ll work for the moment, but eventually they will face the same problem I have. The fix isn’t to use AI to fix the plugin later, but to fix the instructions about making a plugin now. I mean, there’s no reason to still teach the old way of doing things, is there?

---

_[View the full topic](https://meta.discourse.org/t/case-study-of-an-amateur-plugin-author/402084)._