Apple case shows beauty is in eye of software engineer
08 March 2016
The dispute between Apple and the FBI over unlocking the encrypted iPhone used by Syed Rizwan Farook in the San Bernadino (California) shootings last December is being followed with concern by the technology industry, regulatory authorities and the security services in the United States and elsewhere.
An article in ‘The Guardian’ newspaper on February 22 caught my attention when it described the cultural challenges within the Apple security software engineering team in being asked to deliberately break their own software code.
The article explained the almost religious awe in which some engineers hold well-designed software artefacts. Some engineers create astonishingly beautiful software in the eyes of their peers, and become famous in their professional communities as artists. Some accept lower-paying employment to have the opportunity to work in a perfectionist culture rather than just mundane coding. Some would view it almost sacrilegious to deliberately break such software, as the FBI is asking Apple to do.
Elegance of good design
The extreme pride held by some engineers in something being well designed made me reflect on our approach to educating student engineers and innovators. Are our technology students trained to understand the elegance of good design?
The beauty of so much of engineering in our everyday life is inaccessible to most of the public. An electrical or electronic circuit diagram is hardly visually astounding: but the fabric of the design captured by the network of the various interconnections of component symbols may well astonish and delight a professional engineer.
The schematic of an engine, generator, or turbine may appear a maze of cogs, axles and cable: but the insight of the engineer who designed it can only be appreciated by colleagues. The intricate beauty of a software creation can be understood only by those who both have been trained to read code and who have struggled to build polished results.
Architecture is perhaps the only discipline in which engineering design is presented to the public, and soaring cathedrals of beautiful buildings, bridges and towers are impressive. But even then the public rarely has an appreciation of the design decisions and trade-offs buried under the external skin of the construction, leading to an intellectually impressive result.
Of course art forms are also sometimes inaccessible at first sight to the untrained eye, and so unappreciated. Van Gogh died by suicide at 37, having sold just two of his 2,000 or so pieces. Vermeer was forgotten as a minor Dutch artist until two centuries after his death. Keats died of tuberculosis at 25, believing himself a failure. Writing at the time it was produced, the art critic Pietro Aretino complained that not even in a brothel would you see the lurid scenes depicted in Michelangelo’s ‘The Last Judgement’.
The genius of an artist can be deeply appreciated only when the student understands the context. Knowing what has happened before, and with a set of tools and a set of alternatives that could have been adopted, why did the artist choose this outcome over any other? As an example, you can find on the internet the first TV appearance of a young Leonard Bernstein in 1954, in which he explains with reverence the themes Beethoven explored and then rejected while writing his famous symphony No 5.
At the National Concert Hall, BBC presenter Charles Hazlewood has, more recently, led a series of similar analyses of major symphonic works. Analyses and dissections of well-loved literary, poetic and theatrical works are widely available and studied by students of the fine arts. Indeed, our Leaving Certificate humanities examinations are replete in such questions.
Inspiration and understanding
Which brings me back to the way we teach our young engineering graduates and innovators design. In my experience, our students are too frequently taught the tools and norms of the trade and then asked to go away in a class exercise to design and build their own practical work from scratch. Usually assessment is made on whether the submitted exercise “works” rather than, more expansively, how well it is designed to work.
The context and inspiration of what great system designers have achieved, the illuminations and illustrations, and the learning from experience are frequently absent. Inspiration and understanding seems often absent in a vacuum of case studies and exemplars. Unlike education and appreciation in the arts, rarely in the teaching of engineers and innovators is a great design identified, seldom is its architecture explored, and rarely are the reasons the creator rejected alternative structures explained.
Innovation and design requires a combination of left- and right-brain thinking: rational and imaginative, emotional and analytical, ordered and creative. Our education systems frequently present a myriad of tools and rules without context. Too often are our students led down long corridors without understanding the entire floor plan.
Author: Chris Horn, a former president of Engineers Ireland, was the co-founder, CEO, and chairman of technology middleware business IONA Technologies. Dr Horn regularly contributes to debate on Ireland’s high-tech industry and was a member of the ICT working group at IBEC. He currently serves on the board of Gridstore, is chairman of Sophia Search and chairman of Science Gallery International.
This article first appeared in The Irish Times on February 29 (http://www.irishtimes.com/business/apple-case-shows-beauty-is-in-eye-of-software-engineer-1.2549986)http://www.engineersjournal.ie/2016/03/08/apple-case-shows-beauty-is-in-eye-of-software-engineer/http://www.engineersjournal.ie/wp-content/uploads/2016/03/Software-Engineer.jpghttp://www.engineersjournal.ie/wp-content/uploads/2016/03/Software-Engineer-300x300.jpgTechApple