3 ms·
I'm not sure the authors understands what the NIH syndrome (http://en.wikipedia.org/wiki/Not_invented_here http://en.wikipedia.org/wiki/Not_invented_here) is ab
by stewbrew 12y ago
I'm not sure the authors understands what the NIH syndrome (http://en.wikipedia.org/wiki/Not_invented_here http://en.wikipedia.org/wiki/Not_invented_here) is about. It is about writing everything yourself. IMHO the following paragraphe is highly symptomatic for that:
A great mass of libraries, modules, code, and other
software products, available on the net are either
crappy in their own right, or simply not suitable to our
project. Forcing things to work together can be costlier
than simply writing the required code on our own.
In the context of software development, NIH syndrome doesn't mean that you use libraries not invented here but that you re-implement everything on your own.
- wmt 12y agoI think the author understands the NIH syndrome just fine, and starts the whole post describing the IH syndrome as the extreme opposite of NIH pretty well, where one is ready bend over backwards to use a subset of a 3rd party library, even if it might be easier and quicker to implement the desired functionality yourself. Are you afraid to write code? Does the thought linger in your brain that somewhere out there somebody has already done this? Do you find yourself trapped in an analysis cycle where nothing is getting done? Is your product mutating to accommodate third party components? If yes, then perhaps you are suffering from invented-here syndrome.
- stewbrew 12y agoCould be I got lost between thesis and anti-thesis.