3 ms·

I think there are problems where this will apply to, such as crud applications, and projects where deep understanding of core components makes it difficult to s

• hinkley 3y ago
  If the 'core components' are half of the project, there's no core. It's just important and less important components. And in all likelihood if you are expecting a core competency in enough domains for the situation you reference to be true, it's because you have a bad case of NIH, you aren't concentrating your efforts in the areas your company is purportedly focused on. That makes it difficult not only to scale up a team, but also to scale it down. The first major revenue hiccup you encounter may be your last. If you are concentrating on a narrow domain you intend to be experts in, then that will be 15-25% of the code. Meaning to maintain a decent bus number, you only need to be primary on about 10%, if you have half a dozen people or so.