The Admiral’s Pipe

Brad Adams posted this piece. I hope none of *my* management is reading this!

I was recently reminded of a story one of our development managers told me.  Before he started his career in software he was a sailor aboard a Russian sub.  Inspections by the admiral were a regular occurrence and involved a huge investment of time to clean the entire sub… As you might expect Russian admirals were fairly demanding and always expected to find problems.  In fact they kept looking until they found the problem however unimportant they were.  Apparently the sailors came up with a creative way address placate the admiral.  They would leave one, fairly obvious, pipe un-cleaned. The admiral would find this pipe, insist that it be cleaned and feel satisfied that he found a problem and not dig any deeper.  This practice became known as using “the Admiral’s pipe”. 

I will leave it to you to apply this to your work with your own management whether a Russian admiral or IT manager… 

The Admiral’s Pipe

One thought on “The Admiral’s Pipe

  1. I believe that any DataLayer must be a simple code block, that they allow operations against DB.

    That code block would not have to know on the Business Entities. Single to specialize it is to execute the operations (Store Procedures and SQL Sentences) against the engine DB (SQL, Oracle, DB2, etc.), with which this setting.

    Finally, I invite to you to download the DataLayer.Primitives Public Version.

    This is very cool Data Layer 🙂

    DataLayer.Primitives – Readme!


    Javier Luna

Comments are closed.