Warning: Declaration of Jetpack_IXR_Client::query() should be compatible with IXR_Client::query(...$args) in /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php on line 91

Warning: Cannot modify header information - headers already sent by (output started at /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/scratc13/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/scratc13/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/scratc13/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/scratc13/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/scratc13/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/scratc13/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/scratc13/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home/scratc13/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/scratc13/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":45,"date":"2014-11-25T05:02:37","date_gmt":"2014-11-25T05:02:37","guid":{"rendered":"http:\/\/scratchdomain.com\/?p=45"},"modified":"2018-01-13T22:11:40","modified_gmt":"2018-01-13T22:11:40","slug":"never-buy-an-architects-second-house","status":"publish","type":"post","link":"https:\/\/scratchdomain.com\/never-buy-an-architects-second-house\/","title":{"rendered":"Never buy an architect’s second house"},"content":{"rendered":"

So, a few years back a friend of mine used the phrase “Never buy an architect’s second house” as we were discussing the features of a new CNC machine.<\/p>\n

I asked him what he meant and he described a mindset and result that I had seen several times, yet did not have a name for.<\/p>\n

You see, when an architect gets that first house, they are very careful and conservative. They want to get it right. But, the entire time, they are bubbling over with ideas. Things they could add or design to do more things.\u00a0 But, they are too scared to really try on that first house. The first one is overwhelming just in learning the details of how to build that house.<\/p>\n

But, all those ideas are there.\u00a0 Then, comes the second house. That is when the architect tries to add all those ideas. And, then they find the house getting new features and design quirks that clash with each other. The costs go up. The functionality and design begins to clash. The house just does not really go together. No rug will tie the room together.<\/p>\n

After that lesson, the architect dials it back a bit and eliminates good ideas that are really only good ideas in some designs and not others. Eventually, the architect reaches the point where the design and functionality mesh well together.\u00a0This could actually happen on the second or third, or even a little later, but the pattern is almost always the same. There is a steep ramp in ambitions followed by a rather glaring problem, then a ramp back down in what is being attempted. Generally, the more revolutionary the attempt or industry, the further versions are deployed before the crunch. So, a well-known industry like home building will hit early, but a new technology will hit later. Usually in the tech field, it manifests itself in rhetoric promising the world, then a product that sorta does some of what was talked about.<\/p>\n

One of the more notable example comes from NASA. After the loss of the\u00a0<\/em>M<\/a>a<\/a>rs Observer<\/a>\u00a0<\/em>mission, NASA moved to a strategy of smaller less costly missions that were complimentary. So, if a single satellite was lost, we would have others that could still function and gather data. The first mission was Mars Global Surveyor. This was mostly built with existing parts left over from Mars Observer. The same sensors and the like mounted on an off-the-shelf chassis. The second mission was the first one to use really new concepts. That was the Mars Pathfinder mission. Its mission firsts were the rovers and airbag delivery system. The mission was a great success and still shows up in pop culture references.<\/i><\/p>\n

Then, NASA got ambitious. Instead of one mission for the next launch window, they went for three missions. There would be a space probe called Mars Climate Observer, which would orbit the planet and relay back data. The Mars Polar Lander was a second spacecraft. It’s mission was to land in the Mars polar region. The third mission comprised of two probes that were added to the Mars Polar Lander. These probes were to be cut loose from the lander and they were designed to come crashing down into the surface and then try to record sub-surface conditions.<\/p>\n

All three were complete failures,<\/p>\n

Arguably, the Mars Climate Observer was not lost due to ambition. It was lost due to an error in coding. It might have been caught in a simulation or might not have.<\/p>\n

But, the landers were another matter. The penetration probes had very high engineering requirements and a limited budget. There was not a lot of room for testing. They were also on a time crunch to be ready for the next launch window. There was no communication established with the probes, so no specific cause was identified as to their loss, but dropping a probe from orbit into an unknown conditions at high speeds is not a low risk proposition.<\/p>\n

As for the Mars Polar Lander, the most commonly accepted view is that the shipboard computers interpreted the vibration sensors data as indicating the spacecraft had landed while it was still in the descent phase. One reason they think this is a likely cause is because they actually saw this behavior during testing. They launched anyway.<\/p>\n

The next launch window saw only one mission. It was an orbiter with three primary sensors and a communications relay to be used in future missions from the surface.<\/p>\n

The one after that went back to being fairly ambitious, but they dialed back the amount of new things they would try. NASA launched 2 landing missions to Mars in the next launch window. The landers were scaled up pathfinders, but were aimed at areas that were better mapped and where progress could be monitored. The landers had a much larger budget ($850 million for 2 landers vs $110 million for the polar lander).\u00a0 They were also under less of a time crunch.<\/p>\n

They matched their budget to the mission. They limited the number of risks to within reason. They scaled from known working technology and they tested it more thoroughly.\u00a0 Those missions were immense successes.<\/p>\n

Guess the lessons here might be to scale from known to unknown in increments that constitute an acceptable risk. Know what you can deliver and then deliver that. And something well designed can often be in the field long after it’s expected expiration date. Don’t think because you have done something once that you can do everything at once.<\/p>\n","protected":false},"excerpt":{"rendered":"

So, a few years back a friend of mine used the phrase “Never buy an architect’s second house” as we were discussing the features of a new CNC machine. I asked him what he meant and he described a mindset and result that I had seen several times, yet did not have a name for. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_edd_button_behavior":[],"footnotes":""},"categories":[1],"tags":[],"class_list":["post-45","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/posts\/45","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/comments?post=45"}],"version-history":[{"count":11,"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/posts\/45\/revisions"}],"predecessor-version":[{"id":56,"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/posts\/45\/revisions\/56"}],"wp:attachment":[{"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/media?parent=45"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/categories?post=45"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scratchdomain.com\/wp-json\/wp\/v2\/tags?post=45"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}