2 ms·
As frustrating as NIH can be, Never-Invented-Here can be worse. I’ve worked in shops where we were doing some bleeding edge things, either with processes that s
by kstrauser 4y ago
As frustrating as NIH can be, Never-Invented-Here can be worse. I’ve worked in shops where we were doing some bleeding edge things, either with processes that scaled horizontally to levels that were ridiculous at the time, or by handling astounding numbers of events per second, etc. In some of those, we had tech leadership who felt very strongly about using off the shelf components wherever possible, which is fine. Most shops don’t need to re-invent Nginx, or PostgreSQL, or Redis. However, sometimes there’s something unique about a specific problem that means that nothing widely used is going to be a good fit. And in that case, you’ve gotta decide whether to 1) make your engineers solve it with an inadequate tool, 2) find a way to make the problem go away, e.g. by turning away big customers, or 3) trust your engineers to, you know, invent new things.
- fsckboy 4y agoThere's a quite common problem that could be called "Not Invented Here (because we bit off more than we could chew and didn't finish the project, missing the market opportunity)"