Hacker News Reader

Comment by mactat | Hacker News Reader

For me there are two main use cases. First is when you have multiple small repos in the project and you want them to be coherent, you would use shared config file and enforce the structure on ci. Second would be to import best-practice config files to quickly start the project with pre defined dirs/files structure.

View on HN

I understand it at this level, but I'm not sure what coherence there is that's necessary to get.

I can understand, for example, all the Python libraries in the company nesting code under src/ and test/, but that's fairly easy to see and likely never changes after project creation. It's also not really that impactful to dev experience in my experience. Going much further than this feels like it would get too project specific quickly and provide less value.

Do you have examples of the sorts of rules you've seen have most impact?

Couldn't you just create a project template for this?

Don't get me wrong, I think you created a neat project there and it surely has some use, but the argument that this adds a lot of complexity without solving a problem that justifies that kind of complexity stands.

You are correct, especially for smaller project it might add unnecessary complexity, however I still think that for larger ones it might be useful. I’m still trying to figure out which direction should I go with this so thanks for your feedback!

Reply on news.ycombinator.com