3 ms·

It's better than the alternative of not sharing code. Some complex things need to be shared, but something like a library to make directory structures doesn't.

It's better than the alternative of not sharing code. Some complex things need to be shared, but something like a library to make directory structures doesn't. It's fine if teams just write their own, or use one from outside the company. At least that way any issues are limited to only impacting that team, and in the long term you end up with much more maintainable apps. Shared code that isn't treated like an external library(with proper, defined maintainers) is, in my experience, some of the worst technical debt.

alecbz 5y ago
> but something like a library to make directory structure As others comments point out, doing this well is subtle and tricky. This is absolutely the kind of thing that individual teams ought not have to maintain their own copies of. Agree the best solution would be for this to be baked into the language, or failing that a well-known OSS library. But if you don't have either, a shared company library is better than the duplication IMO. It does require a company culture that's able to invest in infrastructure, but I think you need that, especially if you're working with languages like C that don't come with as many "batteries included".