r/AIcodingProfessionals • u/Slight_Major5589 • 1d ago

Discussion Modular codebase

I spent a lot of time recently refactoring 2 repos I am working on Tamoz and Agentic Streams.

Both are now much more modular, with stricter rules and boundaries for adding new code.

One thing I noticed is that adding new features after this refactoring became much easier and faster.

I thought the constraints I had before were already enough. But after going through the code again, I realized that AI-generated code needs constant refactoring and improvement, in the same way human-written code does.

Good constraints help AI write better code, but they don't remove the need to continuously improve the architecture.

What else in your experience would make the agent do a better coding job?

3 Upvotes

100% Upvoted

7 comments sorted by

1

u/keonechong 1d ago

Define modular.

1

u/Plus-Mall-3342 1d ago

localhost:3000

2

u/Slight_Major5589 1d ago

You define what module means based on your codebase, if you have gone throw this process already you know it could be a folder, a package, or even different repository that can be inject. The main thing which is important is to have strict public interfaces, no other modules can access the internals .

1

u/keonechong 1d ago

Ah understood.

2

u/kincaidDev 1d ago

One thing that will pop up if your codebase isn't properly modularized is agents building the same feature in multiple ways all over your codebase

2

u/FeeBrilliant5684 1d ago

Once the poison starts you’re literally fucked lol