# \[TESTING CLAUDE\] Fix an Obsolete Discourse Admin Plugin

**URL:** <https://community.unix.com/t/testing-claude-fix-an-obsolete-discourse-admin-plugin/397437>\
**Category:** Anthropic Claude\
**Created:** [February 15, 2026, 12:54pm UTC](https://community.unix.com/t/testing-claude-fix-an-obsolete-discourse-admin-plugin/397437 "2026-02-15T12:54:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neo](https://community.unix.com/user_avatar/community.unix.com/neo/32/22838_2.png) [@Neo](https://community.unix.com/u/Neo)\
**Post date:** [February 15, 2026, 12:54pm UTC](https://community.unix.com/t/testing-claude-fix-an-obsolete-discourse-admin-plugin/397437/1 "2026-02-15T12:54:01Z")

</div>

I cloned one of my obsolete Discourse admin plugins, and asked Claude to modernize it:

> You have full access right to this discourse plugin: /Users/test/rails/discourse/discourse-container-names-with-gon. please review and insure it is modern and good to go

It told a number of iterations and one crash, but Claude did a great job and this task was completed in record time:

> **[GitHub - unixneo/discourse-container-names-with-gon: This Discourse plugin uses either (A) two...](https://github.com/unixneo/discourse-container-names-with-gon)**
>
> This Discourse plugin uses either (A) two environmental variables specified in the Discourse container yml file or (B) the Discourse system ENV\["DATA\_NAME"\] environmental variable to show the names of the containers in the admin area. In addition, this plugin displays partial disk space information using the df command inside the container.

**Note to self:** _Need to change the plugin name since the `gon gem` is no longer necessary._

The UI results came out better than my original code:

 ![Screenshot 2026-02-15 at 7.46.42 PM](https://community.unix.com/uploads/default/original/3X/f/0/f0b19969ab8d409a617dd9df227be061b743da11.png)

This is amazing. In my spare time today, letting Claude read and write to my filesystem, we (1) created two simple rails apps, (2) one new Discourse theme component and (2) revised an obsolete Discourse plugin.

After those sessions with Claude today, I opined:

> The world will need a lot less programmers in the future, that is for sure!

and

> Yes, this will permit software devs and engineers to be more creative, focusing less on code and more on fit and function

### Claude replied:

> Exactly! It's a shift from "how do I implement this?" to "what should I build and why?"
> 
> Instead of spending hours on:
> 
> - Syntax and boilerplate
> - Debugging typos
> - Reading API docs
> - CSS tweaking
> - Writing repetitive CRUD code
> 
> Developers can focus on:
> 
> - User experience and design
> - Architecture decisions
> - Business logic and requirements
> - Creative problem-solving
> - System integration
> - Understanding the _domain_
> 
> You're a perfect example today - you knew your Discourse infrastructure, understood what sysadmins need to see, had the vision for the plugin's purpose, and made the calls on UX ("fix that wrapping", "add auto-refresh"). I just handled the mechanical parts.
> 
> It's like the transition from hand-drafting blueprints to CAD software. Architects didn't disappear - they just stopped spending time on manual line-drawing and started focusing more on design.
> 
> The creative, human side of engineering becomes _more_ valuable, not less.

### My Final Thought Today After Four Coding Tasks with Claude

It’s true. For this class of deterministic coding, LLMs are already very useful—and becoming more so month by month, as Claude demonstrated today across four tasks. Programming as it was historically practiced will seem as archaic as counting on fingers before calculators and computers automated arithmetic.

When coding is treated as a deterministic task, it can be delegated to an LLM, freeing software developers and architects to focus on system fit, functional design, and architectural intent rather than syntax errors, boilerplate, and manual code entry.
