voidmain42

7 ms·

1. 1.▲
   by voidmain42 9d ago

   I'm pretty late to this thread, but I battled with the whole "keep them organized" issue across 20+ repositories. I see a lot of folks suggesting scripts and symlinks, but I stopped using that approach because filtering (i.e.
2. 2.▲
   by voidmain42 21d ago

   Hi HN. After exiting FusionAuth, I’ve been building a lot with coding agents, and the config sprawl got out of hand. I’d fix something in one repo and forget the other ten. Or I’d start a new repo and have to copy everything over from which
3. 3.▲
   Show HN: One source of truth for agent configs across repos(theagencyhq.dev)

   3 points by voidmain42 21d ago|1 comments
4. 4.▲
   by voidmain42 2mo ago

   Yep. Westminster technically. That's the company I founded. I wrote most of the tools, frameworks, and libraries it uses.
5. 5.▲
   by voidmain42 2mo ago

   It's an ecosystem that includes a number of tools, libraries, etc. The organization (include the GitHub org) is called Latte. Each project is a GH repository under that. The dependency management system is part of the `cli` tool. And t
6. 6.▲
   by voidmain42 2mo ago

   I find that Maven and Gradle are quite complex. Creating a build file for a new project and publishing to Sonatype is extremely difficult. Certainly those projects are solid, but I think there is a lot of room for improvement, and that&#x27
7. 7.▲
   by voidmain42 2mo ago

   I think that's why other platforms have done so much better than Java. NPM, Python, Ruby, DotNet, etc. They all have dependency management, versioning, publishing, repository management, HTTP, web frameworks, and build tools as one com
8. 8.▲
   by voidmain42 2mo ago

   I'm the author of Latte. Some of the projects are actually forks from some of my open source from the company I founded (and later sold). Some have been around for quite a while (10+ years) and have some adoption as well. To keep those