The method Well no, see, that’s the tricky part. I always try to come up with things that when they find out the method, the method is as interesting as the effect itself. — David Blaine Richard Saul Wurman, Understanding Understanding magic
Ancient magicians as innovation consultants An Article by Matt Webb interconnected.org The Codex Justinianus (534 AD), being the book of law for ancient Rome at that time, banned magicians and, in doing so, itemised the types: A haruspex is one who prognosticates from sacrificed animals and their internal organs; a mathematicus, one who reads the course of the stars; a hariolus, a soothsayer, inhaling vapors, as at Delphi; augurs, who read the future by the flight and sound of birds; a vates, an inspired person - prophet; chaldeans and magus are general names for magicians; maleficus means an enchanter or poisoner. I happen to have spent my career in a number of fields that promise to have some kind of claim to supernatural powers: design, innovation, startups… It’s not hard to run through a few archetypes of the people in those worlds, and map them onto types of ancient magician. Those like Steve Jobs (with his famous Reality Distortion Field) who can convincingly tell a story of the future, and by doing so, bring it about by getting others to follow them – prophets. Inhaling the vapours and pronouncing gnomic truths? You’ll find all the thought leaders you want in Delphi, sorry, on LinkedIn. Those with a good intuition about the future who bring it to life with theatre, and putting people in a state of great excitement so they respond – ad planners. Haruspex. Those who have the golden mane of charisma: enchanters. Startup founders. People with a great aptitude for systems and numbers, who can tell by intuition what will happen, from systems that stump the rest of us. We call them analysts now. MBAs. Perhaps the same aptitude drew them to read the stars before? Mathematicus. Steve Jobs: The Lost Interview magicinnovation
-2000 Lines Of Code An Article by Andy Hertzfeld www.folklore.org Bill Atkinson...who was by far the most important Lisa implementor, thought that lines of code was a silly measure of software productivity. He thought his goal was to write as small and fast a program as possible, and that the lines of code metric only encouraged writing sloppy, bloated, broken code. ...He was just putting the finishing touches on the optimization when it was time to fill out the management form for the first time. When he got to the lines of code part, he thought about it for a second, and then wrote in the number: -2,000. I'm not sure how the managers reacted to that, but I do know that after a couple more weeks, they stopped asking Bill to fill out the form, and he gladly complied. The amount of work not done metricscodemanagementproductivity