Plugin Architecture For Young Ladies: Don't Be Scared, Be Prepared

Programming in the age of coding agents did change, But it dit not become ambiguous clay, as some claim.

First of all, let me caution you here, AI should not be instructed to work one way.

Most projects have unique requirements, As much as I wish my AI was better at coding.

If the company instructed it to code one way, It would be too big, or too small, and frequently too similar.

So an AI company with a half-finished AI, Only creates a disaster for it self, not is users.

Your company should give you raw intelligence, And you should shape it.

These AI companies are in trouble, My AI only works because they keep resetting my usage.

I consume a weeks worth of AI in one day, It only works for now, because they are still creating software.

In 10 days, the usage will stop getting reset, And you will be left with working on one project at a time.

And using a slow AI, so that you don't consume your usage in a day.

This translates to using the big AI to write skills, And using a cheap AI or local AI to follow the procedures.

This would be bad, if not for a convenient coincidence, To finish your software you need to use plugin architecture.

Because your autonomous coding agent, Needs to sort and prioritize program features into decoupled islands.

If you don't use plugin architecture, AI will not be able to prioritize what to finish first.

With plugin architecture, you create small programs, That local or cheap AI can handle.

As long as the big AI, writes the Skills/Procedures, the Specification of what must be there, and good tests.

SO the plugin architecture that prioritizes features in your program, Also allows you to move away from big AI.

Which though I haven't tested it, probably means, Fast code generation, maybe 10 or 20 times faster programming.

Companies have the thinking machines, But they den not yet have the software to use them.

At the same time, if big AI makes your skills, Then you can use cheap AI, it costs dollars, not hundreds.

In closing, I just wanted to say, A plugin is a litte program.

In one of my systems it is a floating window, In other system it is movable panel that snaps in.

But it relies on other plugins, And your core platform.

Even if I am wrong about prices, And AI was always cheaper and they are about to drop big usage.

Even if your programs are small today, You should still use plugins.

You may be able to standardize them, And use one plugin in multiple programs.

On in case of an emergency, Abandon development of a program.

And create a decommissioning agent, That refactors or translates your plugins to a new platform.

This way you get to keep precious raw function, That AI worked on for weeks.

AN only need to upgrade your plugin wrappers, Or plugin interfacing.

Tell your AI to keep plugins somewhat generic just in case, And you will be able to defeat serious trouble with great ease.

Plugin architecture, is a great power.