Hacker Newsnew | past | comments | ask | show | jobs | submit | verma6uc's commentslogin

This is the exact problem we built Glue to solve. Maintaining markdown files per subsystem works but breaks down as the codebase evolves — the docs drift from reality within weeks. Glue keeps a live, queryable map of the codebase that updates as code changes, so you're not repeating the assessment or trusting stale docs. Happy to share more if useful — getglueapp.com


This is exactly what we're seeing building Glue. Writing code got cheap but understanding a codebase didn't — it might have actually gotten harder because there's more of it. We built Glue for the PM and EM who needs to answer "what does this codebase actually do?" without reading every file the AI just generated. The problem isn't generation anymore, it's comprehension and ownership. Curious if others are building tooling around this.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: