๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

Artem
@sl1ma4
Founder of Open source uptime monitoring and status pages, in Rust. Bootstrapping in public.
๊ฐ€์ž… February 2010
1.9K ํŒ”๋กœ์ž‰ ์ค‘    2.3K ํŒฌ
Uncle Bob just released a pretty cool tool for visualizing software architecture: uml-viewer ๐Ÿ”ฅ I pointed it at my Uptimepage repo. and yeah... the dependency graph was a mess ๐Ÿ˜‚ 6 commits and 315 files later: - dependency violations: 167 โ†’ 109 - circular dependencies: 35 โ†’ 3 - modules importing api: 17 โ†’ 4 - app rs: 1087 โ†’ 642 lines 32 dependency cycles eliminated. domain, storage, security, and config no longer depend on API handlers. no behavior changes. the best part? I could actually see where the architecture was broken, tell the agent what to fix, and check the result in the graph. way better than asking AI to "refactor the codebase" and hoping for the best.
๋” ๋ณด๊ธฐ