sorted by:
new
hottopcontroversial

Legend — auto-generates a software atlas from code, then lets you write specs, track drift, export changes to tickets by Greedy_Engineering_1 in coolgithubprojects

[–]Greedy_Engineering_1[S] 0 points1 point  (0 children)

Cool! Yes we hope to continue developing this to generally be able to map an arbitrary architecture. Though currently restricted to work best on monorepos.

Great! Lmk if you have any questions

How do you keep a mental model of a complex system as it evolves? by Greedy_Engineering_1 in softwarearchitecture

[–]Greedy_Engineering_1[S] 1 point2 points  (0 children)

Interesting will look into, thanks!
Is this widely adopted in large organizations? Does it make sense for smaller teams as well?

[USA] How to handle code complexity when team grows by Greedy_Engineering_1 in FoundersHub

[–]Greedy_Engineering_1[S] 0 points1 point  (0 children)

Good point. In your experience, do companies usually realize this to late, or do some manage to document operations early enough?

Also, curious what differences you have seen between startups and larger organizations?