r/softwarearchitecture • • 19h ago

Tool/Product CodeNib: a wiki and architecture map generated from your repository

Thumbnail gallery
17 Upvotes

CodeNib is an open-source tool that writes a wiki for a repository. The wiki starts from a map: each area of the code is assigned to a node, and arrows show their relations in the code.

Every area has its page. The overview page starts at a public entry point and walks the main call path step by step, and each step has its location in the repo.

Wikis to browse, no account needed:

For your own repository, the CodeNib Wiki GitHub Action is one workflow file. It writes the pages in your CI with a model key you provide, publishes them to GitHub Pages, and stay synced with your code in main.


r/softwarearchitecture • • 8h ago

Discussion/Advice Plato's Sophist and Statesman are basically SWEs modeling sessions

13 Upvotes

He basically just exposes in poetic words a large class hierarchy he already created(probably in his working sessions). He was worried about same questions SWEs were worried just few years ago - how to create a right abstraction, how to create correct subclasses out of one main class (to "cut" class into several subclasses).

It seems to me he also did architectural diagrams (modeling), but we don't have any artifacts of him using UML or something similar.


r/softwarearchitecture • • 18h ago

Discussion/Advice Explicit state machines and AI

12 Upvotes

Hi,

I've been a SWE for 7 years. I mainly did full stack with Java backend applications that are essentially CRUD.

I'm currently experimenting with a kind of fully automated development process via AI agents and found that telling the AI to use explicit state gave very good results whereas without I always had issues like buttons that shouldn't be there. E.g. a delete button that I could press even though I did not even create the entity yet.

I am wondering why I never encountered explicit state machines in my projects. I guess it creates too much overhead and cost for most projects. And for most projects it is not a big deal to just have implicit state machines. But with the emergence of AI coding I have a feeling that explicit state machines should become a standard in any software project. Or am I missing something?

I also feel like they will become the aspect of the code that humans can better review and own in a time where the software becomes more and more like a black box.

Edit:

What I am essentially trying to figure out is, if it will be ever detrimental if I tell AI to do explicit state machines in all of my projects?


r/softwarearchitecture • • 14h ago

Discussion/Advice Intern with no seniors around, how do I get better at AI-assisted development and actually understand what I'm shipping? Looking for genuine advice.

8 Upvotes

I recently joined a new tech company as an intern after a year-long gap. Before this, I did a 6-month remote front-end internship at a startup, where I handled the entire front-end and one other guy did the back-end. I knew the concepts and basics of front-end languages and frameworks, but I vibe coded pretty much all of it.

Now I'm at a company where everyone is a junior and everyone is figuring things out on their own. There's no senior developer, not even in the whole company, so nobody to tell me what to look at or what to do when something breaks. The framework and even the language are new to me, and I'm still vibe coding with LLMs. The problem is they're non-deterministic. Sometimes they "fix" stuff in the codebase that I never asked them to touch, and I can't always tell whether the change is right.

I'm not trying to give up AI. I want to use it better. My goal is to understand the code and the architecture well enough that when an LLM writes something, I know what's going on and can judge whether it's right. I also want to get good at system design and prompting so I can eventually take a project from start to deployment on my own with AI assisting me. I've heard about agents.md and skills files but have never actually tried them.

My learning style is a bit of a problem. I'm a read-everything, one-shot kind of person, not a step-by-step one, and I forget things quickly, so I often feel dumb. I've watched dozens of talks and interviews on this, but nothing stuck because I always fall back on my old way of learning. I know I should change it, but I'm lazy and don't know where to start.

On the infra side, the team sets up servers manually and has no CI. I ran a homelab before and I'm comfortable with Linux, hosting and deploying, so I could probably help. But I'm new and don't want to step on anyone's toes.

If you're an experienced dev, how would you learn an unfamiliar stack with no mentor, use AI without losing the learning, and maybe bring up CI and deployment as the new intern?

I'd also love to hop on a call with anyone who's up for it, to go deeper. Happy to chat about whatever works for you. Thanks a lot! Resources are appreciated


r/softwarearchitecture • • 11h ago

Discussion/Advice How do you manage business rules that change more frequently than your application code?

0 Upvotes

A question for software architects:

How do you manage business rules that change more frequently than your application code?

In many systems, pricing, eligibility, validation and approval logic end up scattered across services, buried in conditionals and understood by only a few developers.

Would you rather:

  • Keep them in application code?
  • Use a dedicated rules engine?
  • Manage them through decision tables?

I'm interested in how teams handle testing, versioning and auditing when business rules change.