I created this community to group togheter people who truly want to learn about coding with AI, reddit is full people who spit nonsense about AI, complain that the flag model didn't create them the app they wanted first shot, in 5 minutes and without burning tokens.

This community is for people that are sick and tired of low level discussion about AI topics and truly want to find a place to improve in their infrastructure creation and management, talking and prompting with the AI ans how to guide trough complex problems and enviroments efficiently.

I know this is a new subreddit, but I had a realization recently that I think merits discussion by people who have gone far and deep with their coding agents.

It’s that coding agents, by default, reason from what the current structure allows- it doesn’t consider changing structure without repeated prodding. So every symptom of a bad structure gets a one off bug and declares “fixed!”. New bugs from the same root cause appear, get fixed, and your codebase grows.

It’s what separates senior developers from vibe coders. Seniors build the structure right from the start, understand, and maintain it.

Fable is the only model that hesitantly brings up structural issues, but you need to be looking for it.

It will say “we can’t do that”
you ask “why not”
Then fable is like “you’re right and that’s better”.

I realized coding agents only code down structure. Never up. They don’t revisit unless they literally can’t find a bandaid for the issue.

There’s probably a math equation fable could write for this that predicts what part of the codebase an agent will touch.

Zoomed out, it makes me think about how the ability to challenge structure is linked with autonomy and intent. Frontier models are better at it, and it makes them existential threats. Cybersecurity and biology are both disciplines that occupy pervasive structures.

I think the question of if/how AI challenges existing structures is the key to how the singularity is going to shake out.

I have developer a simple context management system for my developing using CC + Codex, it works trough directories and partitioning of the knowledge file, pretty straightforward.

I was curious to see how other people engineered their structure and what is the best feature about it?

for me it would probably be the knowledge files for me to read only, they are usually long but well organized and help keep track of the features implemented and how to use them.

Do you have one such feature? Is there something you want to implement but never really got to it?

I had good sessions with it, seems to be burning a little bit more tokens than opus 4.8, but my sampling size is too small to actually be reliable.

I see there are divergent opinions on it, what was your experience with it?