I had an interesting day yesterday, took a project that I have
been nurturing from conception, with the client, to the
engineering works who will be building it.
Before I get into that, there is something that needs to be
explained.
When I turn up with documentation and drawings and artwork and
all the other biz, you are in effect looking at a picture that an
artist has painted.
You can look at the picture and admire it and say what you see,
but you cannot have any hope of knowing or understanding why or
how each part of that picture got painted.
You cannot look at the Mona Lisa and see the paintings that
Leonardo did not paint in order to paint Mona, you cannot look at
it as see the order in which certain methods of painting were
rejected, and why, you cannot look at it and see what Leonardo
was trying to paint either.
Not Invented Here (NIH) vs Form Follows Function (FFF) crackles
into life like Frankenstein's monster.
So there we are, sat in a circle, I'm showing my stuff, and
the youngest guy in the "crew" is effusive, keen, and
asks all the right questions, while the older guys are nice, but
I can see the "Not Invented Here" gleam in their eyes.
Thankfully for me I'm old enough and ugly enough that
I've been there before, so all the documentation is littered
with references that, with 20/20 hindsight, will make every
instance of NIH hard to justify. I'm also old enough and ugly
enough to know that in engineering Form Follows Function, there
are only so many ways in which you can vary the design of a
straight razor and still have a useful straight razor.
But NIH means that instead of taking a body of work that clearly
represents a far greater hidden body of thought, and then using
that as a starting place and grilling the artist, people prefer
to start with a blank sheet, and duplicate every last bit of
effort, while the combination of NIH and your body of work means
they will try and repeat it in such a way that it is unmistakably
"all their own work" and not a clone or derivative of
your work.
The loser in this scenario is FFF, FFF has to be sacrificed to
NIH.
My design was elegant in its simplicity, excluding fasteners
(socket screws etc) which are all hidden anyway, presenting a
nice clean design, it comprised of 84 parts in total, and that
pile of 84 parts was made up from only 24 unique parts. My design
was simple and fast to manufacture and assemble, I could walk
into a machine shop and have short runs turned out for 500 quid a
pop.
More importantly, my design was 100% FFF, there was no precedent
so NIH didn't make an appearance, so my design just plain
works.
At this point I should perhaps admit to enough experience and
arrogance that frankly I don't care that much if NIH means
the design never makes it as a commercial product, as far as I am
concerned my design is pure FFF and does not require any further
external "validation" by hitting shelves. _I_ know it
is *bloody* good. That is enough.
But all the personality faults and foibles of the character set
that makes up a good engineer asise, this whole issue of NIH vs
FFF is
an interesting and important one all by itself, and an issue that
is not dealt with adequately by the likes of wikipedia.
While the next 3 to 6 months will be interesting for me
personally, as it await the end result of the NIH vs FFF dynamic,
far more interesting is the human aspect, and the implications,
as this NIH vs FFF scenario is far more common in day to day life
than people imagine, and far more pervasive.
NIH is, in my experience, symptomatic of maturity and time spent
in a stable environment, it is symptomatic of not exploring the
boundaries, it is symptomatic of committee peer review, whereas
FFF is symptomatic of a more youthful approach, one which pays
less attention to the benefits of a stable environment, less
attention to the opinions of others, and more attention and focus
on discovery and research and personal growth and opportunity.
The one young engineer who instinctively grasped what I was
presenting from a FFF viewpoint and wanted to run with that ball
was also the only one who took the time and effort to bring to
the meeting a sample of the device that this product will work
with (please do not ask me to be more specific about this, it is
irellevant to the discussion) and to try to work the whole thing
together in his head.
The more mature engineers instead instinctively grasped the data
I was presenting as a broad outline on canvas, an art from, in
oils, a portrait of the mona lisa, and what they brought to the
meeting was an eagerness to collaborate on creating a series of
copies of a new portrait of a young woman, maybe in oils, maybe
not.
Years ago in my youthful, rebellious, HD riding days I owned a
tee shirt, blain black, with white lettering, it said;
"As you are now, I once was. As I am now, you will never
be."
The point being the young FFF engineer may survive to become an
old FFF engineer, but the fact that most young engineers are NIH
and that most environments with older engineers are NIH means
that the likelihood is that he will turn from a young FFF
engineer into an old NIH engineer.
Which is a shame.
It is a shame from everyone's point of view.
It is a shame from the client's point of view, because it
means that things that have absolutely nothing to do with
engineering or product marketing, but everything to do with
conservatism, will be the most important and influential factors
is determining whether or not his brainchild ever hits the
shelves.
It is a shame from the publics point of view, because it means
that the stuff they are able to buy has been built to
conservative values that have nothing to do with the product and
everything to do with the personalities and culture of the
builders.
It is a shame from an economics point of view, because vast
amounts of original effort are simply discarded, and vast amounts
of effort are duplicated time after time, as NIH takes precedence
over FFF.
Now I'm no Leonardo, but I'll bet body parts that his
attitude about his work was the same as my attitude about mine,
he didn't care what Tom, Dick or Harry thought of it, he did
it for himself (even if he was paid and commissioned) to please
himself, and it is only an accident of fate that some of those
things survive to this day, and have won almost universal acclaim
for their beauty.
I met and occassionally conversed with one of the descendants of
Juan Miro,
and he was the quintessential essence of not giving a damn what
other people thought of his work, and I remember quite clearly
being told that his own favourite examples of his own work were
simply ignored, much less merely misunderstood.
Miro understood NIH vs FFF, he understood first forming the
opinion, then looking at the art, and any oft enough repeated
opinion becomes a Way Of Life, the opinion holder becomes a
Conservative Thinker.
I have deduced that the flux in balance between the proportions
of NIH and FFF varies pretty much in tune with the state of
society during the formative years of the citizenry, in easy
times living off the fat of the land we get very few FFF
thinkers, in tougher times we get a far greater proportion of FFF
thinkers, but the NIH thinkers are always there, like a governor,
to prevent the FFF crowd from inventing transport devices so fast
they will suffocate the passengers, bombs so powerful they will
consume the entire atmosphere of the planet, and grey goo so
avaricious it will consume everything it touches.
Science Fiction, Horror Stories, even the more mundane social
manias from the You Tube generation excesses to Man Made Global
Warming and Enviromental Collapse, all, in my mind, are examples
of the perennial struggle between NIH and FFF.
My own little creation. It doesn't amount to a hill of beans.
The most interesting thing about it, by far, is the NIH vs FFF.
Programming is like playing chess. To be great you need to
start early and have an natural aptitude. You can teach any
college graduate to play chess, but you cannot teach them all to
be great. If we are in the business of playing chess, it
makes sense to hire a Kasparov who costs a lot but can win 100
matches simultaneously, than it does to hire a committee of
college grads.
Thus, computer programs can resemble chess matches. You can
define a chess match in merely 40 moves, but that is little
indication of the thought processes involved to create it.
All design problems are like this, in that they can look
deceptively simple once solved correctly.
Alternatively, you can just ban Kasparov (perhaps because of his
politics or hey, just make something up because perhaps you are
liable to his mother and want to make sure that the family is
never in a position to pursue claims). Make a business model out
of hosting big money tournaments for patzers -- which is roughly
the actual situation in software. Yeah, you have to pay out big
to to the best among the patzers but, meanwhile, you more than
make it up in fees.
Anyway, chess is a lousy analogy for "all design
problems". Yeah, yeah, every chess move involves using some
judgment to balance a bunch of constraints -- it's vaguely
similar to engineering that way. The problem with the analogy is
that chess is a lot more like poker than people generally
acknowledge. It's a "partial knowledge" game for
2/3's of the game. Long term strategic decisions about
massive engineering efforts are "partial knowledge"
like that but most work is vastly more certain.
I'm no mech. e. but in Guy's case, for example, he's
talking about the reasoning behind various design elements that
are too deep to elaborate on in a quick presentation. Why use
this screw here? Why that material there? For those, he's got
fairly objective answers (I presume). In chess, you get poker
heuristics instead: "Oh, I wanted to develop the middle. Oh,
I wanted to bring out my knights early. Gosh, I wanted to attack
his right side." There are fairly deeply analyzable
triangulations of positions in chess but understanding those
conveys only "good patzer" levels of skill. The rest is
very social, very "partial knowledge" -- in every way
poker.
It's funny how the modern meaning of cynic is in some ways
twisted 180 degrees from whence it came, and in some ways not.
The deliberately homeless types who live like dogs, bark at
perceived enemies, and lack shame: you don't much hear them
called cynical, these days. Rather, the term tends to be reserved
for those who revel in power and who take material accumulation
and consumption to be synonymous with virtue. The only constant
element, over the years, is the absence of a capacity for shame.
The term is unfair to dogs, in that sense. Dogs have a capacity
for shame. Smart and well socialized dogs even have a sense of
social propriety. Cynics, ancient and modern, lack those things.
In modern times, the word cynic is often used to convey a
personality characterized by relentless disingenuity. Well,
that's putting it imprecisely. Sociopathy is closer to the
mark: a habit of wielding the forms of civil society, as a
kind of shield - a habit of "plausible deniability",
yet all the while rejecting the intention of those forms
and thereby inverting their meaning.
The best way to refuse to cooperate or negotiate in many civil
circumstances is to flawlessly deliver a pro forma simulacrum of
(false) offers to cooperate and negotiate. This is the modern
cynic. The cynic lacks capacity for shame.
I submit, Guy, that the dynamic you refer to there isn't
about NIH. It's about "what's my job?" I mean
this:
NIH is about ego and lack of trust. NIH syndrome is a consistent
pattern of overestimating the cost of "taking" and
under-estimating the cost of "making". NIH syndrome is
characterized by a consistent pattern of lacking trust in the
capacity of others to be able to generate a better idea.
That's all it is.
But, "what's my job" sounds like what you are
talking about. The "what's my job" syndrome
isn't about overestimating one's own capacity to do much
of anything useful and it isn't based in an assumption that
better solutions can't come from outside. Rather,
"what's my job" is based in shamelessness and fear.
If you try to bring into a project someone suffering from
"what's my job" syndrome, their dominant patterns
of thought through the entire process revolve around how it is
that they'll come out of the project with a veneer of
irreplaceability. You and I know that if a senior engineer simply
reviews some plans submitted and rightfully reaches the
conclusion that "this is excellent work; I approve"
that said senior engineer has made an incredibly valuable
contribution. But the cynical senior types (engineering and more
commonly management) lack shame and suffer from fear -- they are
always calculating their list of excuses, explanations,
lines to add to a CV. In short, always fretting over how to make
unassailable "arguments" for their security and
advancement, with little regard for actually useful work
accomplished.
You and I know that the senior guy who whistles in admiration and
says: "that's damn good, go for it" should be
entitled to and should take the rest of the month off. Go
fishing. Maybe come back at the end of the month with a couple of
ideas to make it even better - or maybe come back with a clearer
idea of why it's just right as it stands.
The cynic knows no such thing. The cynic's bravado is a cover
for constant panic. The thinking is: "If that's so good,
and I didn't do it, then what's my job?"
The cynic is sociopath and hence charmer, often offering up a
convincing simulacrum of one who has their head on straight and
simply enjoys the good things in life. The modern cynic serves up
great wine. The successful modern cynic is an A-list speaker or
guest. The successful modern cynic can not open their mouth but
to dissemble and always with a heavy subtext message of their own
centrality and importance.
NIH is just a particular kind of common mistake in judgement.
"What's my job?" is a way of life.
Not Invented Here vs Form Follows Function
I had an interesting day yesterday, took a project that I have been nurturing from conception, with the client, to the engineering works who will be building it.
Before I get into that, there is something that needs to be explained.
When I turn up with documentation and drawings and artwork and all the other biz, you are in effect looking at a picture that an artist has painted.
You can look at the picture and admire it and say what you see, but you cannot have any hope of knowing or understanding why or how each part of that picture got painted.
You cannot look at the Mona Lisa and see the paintings that Leonardo did not paint in order to paint Mona, you cannot look at it as see the order in which certain methods of painting were rejected, and why, you cannot look at it and see what Leonardo was trying to paint either.
Not Invented Here (NIH) vs Form Follows Function (FFF) crackles into life like Frankenstein's monster.
So there we are, sat in a circle, I'm showing my stuff, and the youngest guy in the "crew" is effusive, keen, and asks all the right questions, while the older guys are nice, but I can see the "Not Invented Here" gleam in their eyes.
Thankfully for me I'm old enough and ugly enough that I've been there before, so all the documentation is littered with references that, with 20/20 hindsight, will make every instance of NIH hard to justify. I'm also old enough and ugly enough to know that in engineering Form Follows Function, there are only so many ways in which you can vary the design of a straight razor and still have a useful straight razor.
But NIH means that instead of taking a body of work that clearly represents a far greater hidden body of thought, and then using that as a starting place and grilling the artist, people prefer to start with a blank sheet, and duplicate every last bit of effort, while the combination of NIH and your body of work means they will try and repeat it in such a way that it is unmistakably "all their own work" and not a clone or derivative of your work.
The loser in this scenario is FFF, FFF has to be sacrificed to NIH.
My design was elegant in its simplicity, excluding fasteners (socket screws etc) which are all hidden anyway, presenting a nice clean design, it comprised of 84 parts in total, and that pile of 84 parts was made up from only 24 unique parts. My design was simple and fast to manufacture and assemble, I could walk into a machine shop and have short runs turned out for 500 quid a pop.
More importantly, my design was 100% FFF, there was no precedent so NIH didn't make an appearance, so my design just plain works.
At this point I should perhaps admit to enough experience and arrogance that frankly I don't care that much if NIH means the design never makes it as a commercial product, as far as I am concerned my design is pure FFF and does not require any further external "validation" by hitting shelves. _I_ know it is *bloody* good. That is enough.
But all the personality faults and foibles of the character set that makes up a good engineer asise, this whole issue of NIH vs FFF is an interesting and important one all by itself, and an issue that is not dealt with adequately by the likes of wikipedia.
While the next 3 to 6 months will be interesting for me personally, as it await the end result of the NIH vs FFF dynamic, far more interesting is the human aspect, and the implications, as this NIH vs FFF scenario is far more common in day to day life than people imagine, and far more pervasive.
NIH is, in my experience, symptomatic of maturity and time spent in a stable environment, it is symptomatic of not exploring the boundaries, it is symptomatic of committee peer review, whereas FFF is symptomatic of a more youthful approach, one which pays less attention to the benefits of a stable environment, less attention to the opinions of others, and more attention and focus on discovery and research and personal growth and opportunity.
The one young engineer who instinctively grasped what I was presenting from a FFF viewpoint and wanted to run with that ball was also the only one who took the time and effort to bring to the meeting a sample of the device that this product will work with (please do not ask me to be more specific about this, it is irellevant to the discussion) and to try to work the whole thing together in his head.
The more mature engineers instead instinctively grasped the data I was presenting as a broad outline on canvas, an art from, in oils, a portrait of the mona lisa, and what they brought to the meeting was an eagerness to collaborate on creating a series of copies of a new portrait of a young woman, maybe in oils, maybe not.
Years ago in my youthful, rebellious, HD riding days I owned a tee shirt, blain black, with white lettering, it said;
"As you are now, I once was. As I am now, you will never be."
The point being the young FFF engineer may survive to become an old FFF engineer, but the fact that most young engineers are NIH and that most environments with older engineers are NIH means that the likelihood is that he will turn from a young FFF engineer into an old NIH engineer.
Which is a shame.
It is a shame from everyone's point of view.
It is a shame from the client's point of view, because it means that things that have absolutely nothing to do with engineering or product marketing, but everything to do with conservatism, will be the most important and influential factors is determining whether or not his brainchild ever hits the shelves.
It is a shame from the publics point of view, because it means that the stuff they are able to buy has been built to conservative values that have nothing to do with the product and everything to do with the personalities and culture of the builders.
It is a shame from an economics point of view, because vast amounts of original effort are simply discarded, and vast amounts of effort are duplicated time after time, as NIH takes precedence over FFF.
Now I'm no Leonardo, but I'll bet body parts that his attitude about his work was the same as my attitude about mine, he didn't care what Tom, Dick or Harry thought of it, he did it for himself (even if he was paid and commissioned) to please himself, and it is only an accident of fate that some of those things survive to this day, and have won almost universal acclaim for their beauty.
I met and occassionally conversed with one of the descendants of Juan Miro, and he was the quintessential essence of not giving a damn what other people thought of his work, and I remember quite clearly being told that his own favourite examples of his own work were simply ignored, much less merely misunderstood.
Miro understood NIH vs FFF, he understood first forming the opinion, then looking at the art, and any oft enough repeated opinion becomes a Way Of Life, the opinion holder becomes a Conservative Thinker.
I have deduced that the flux in balance between the proportions of NIH and FFF varies pretty much in tune with the state of society during the formative years of the citizenry, in easy times living off the fat of the land we get very few FFF thinkers, in tougher times we get a far greater proportion of FFF thinkers, but the NIH thinkers are always there, like a governor, to prevent the FFF crowd from inventing transport devices so fast they will suffocate the passengers, bombs so powerful they will consume the entire atmosphere of the planet, and grey goo so avaricious it will consume everything it touches.
Science Fiction, Horror Stories, even the more mundane social manias from the You Tube generation excesses to Man Made Global Warming and Enviromental Collapse, all, in my mind, are examples of the perennial struggle between NIH and FFF.
My own little creation. It doesn't amount to a hill of beans.
The most interesting thing about it, by far, is the NIH vs FFF.