Never Invented Here

2015/03/29 11:32

Michael O. Church on the 'Never-invented here' syndrome prevalent in Software development organisations:

if engineers are micromanaged to the point of having to justify weeks or even days of their own working time, not a damn thing is ever going to be invented, because no engineer can afford to take the risk; they’re mired in user stories and backlog grooming. The core attitude underlying “Agile” and NeIH is that anything that takes more than some insultingly small amount of time (say, 2 weeks) to build should not be trusted to in-house employees.
-- Never Invent Here: the even-worse sibling of “Not Invented Here”

... and the problems of job satisfaction and employee retention in same:

In a never-invent-here culture that just expects programmers to work on “user stories”, the programmers who are capable of more are often the first ones to leave.

The whole blog post is very nuanced and well worth a read. I'll leave with this...

The failure, I would say, isn’t that technology companies use off-the-shelf solutions for most problems, because that is quite often the right decision. It’s that, in many technologies, that’s all that they use, because core infrastructure and R&D don’t fit into the two-week “sprints” that the moronic “Agile” fad demands that engineers accommodate, and therefore can’t be done in-house at most companies. The culture of trust in engineers is not there, and that (not the question of whether one technology is used over another) is the crime. -- Never Invent Here: the even-worse sibling of “Not Invented Here” | Michael O. Church


Programming, Agile