So when you’re against the clock working to complete a task, how much of your time should be spent massaging the ego of a recalcitrant software package? How much should the average user need to know about stability, memory leaks and the like? Looking back on it, a very significant portion of an operator’s time is spent corralling the code in a particular direction, working with the various foibles and “features”, well aware that autosave is not always there to save you, erm, automatically. This is totally off the top of my head, but I reckon that a good 20-50% of your time working on any given “productivity tool” is actually spent working within the limitations and boundaries set out by a Russian programmer called Petr. Or Vlad. Whilst my claim is no more accurate than a certain outgoing president’s claims of electoral fraud, unlike electoral fraud a loss in user productivity is really important. This is largely because large organisations like to make decisions based upon perceived percentages of productivity gain, versus sticking with existing legacy solutions, often sold to them by some vendor’s overzealous customer relations managers. Bold improvements in productivity are often trumpeted on marketing bumf but seldom is it mentioned that a certain proportion of that percentage improvement will be lost to “fucking about whilst the little beachball thing spins around”. Go to any busy design studio tomorrow and you can guarantee that at least one user has popped off to take a dump instead of sitting watching a percentage bar crawl across the screen.

To the nearest zillion, how many of these do you think Autodesk receive every quarter, filled with expletives?

I would be very interested to know what the actual percentage productivity gain there is from, say Revit 20xx, versus all the time lost to discovering new and wonderful bugs in this the latest iteration. Rather than always rushing to regurgitate the latest juicy morsels to the impatient hungry chicks, why not slow it down a bit? Mummy and daddy bird could eat together and stop off at the shops on the way home to pick something up for the kids. They could even get some groceries in and prepare something fresh using the cookery book by that fashionable celebrity chef when they get home. Exactly how this applies in the context of software development I’m not sure, but the point is that software development is so frenetic that there is barely a window of stability long enough when everything stops moving around for anyone to measure whether all these new, whizzy patches and add-ins are really helping as much as the vendors claim.

Now of course the image of a garden bird in chefs whites presenting Jamie Oliver style to mums wanting to improve their kitchen repertoire, is absurd. But then they were saying that about a Donald Trump presidency, and look what happened to that? Slow down the product cycle, I say, and aim to provide a competent core product that suits the majority of day to day users, instead of chasing some BIM panacea that so far has largely failed to materialise. Then, the true productivity gains can be gauged over a longer term, in a stable and reliable way, without all the bluster of the bestest and latest update muddying the waters. Also, I like the idea of little birdy chefs.

By Bim Weasel

Born in 1900, in a block of cheese, Bim Weasel has had to struggle from day one. After eating his way out, bursting forth, like some kind of pasteurised Alien alternative, he began trading nuts and seeds before moving on to complex financial derivatives. After making his first million at the tender age of 13 and three quarters, he diversified into commodities. The outbreak of the First World War saw his fortunes rise yet further, as now the owner of copper, bauxite and iron mines in Papua New Guinea and Australia, and rubber plantations in the Dutch East Indies, his holdings shot up in value. The next decade saw Bim spend his fortune on women and fast cars, whilst the rest he just wasted. By the outbreak of World War Two, Bim was destitute and living as a tinker and shoe repairer in a coastal village in Sulawesi. Despite not being a Dutch national, his love of the colour orange saw him interned by Japanese Imperial forces. He was sentenced to execution and only saved at the last minute by a young Jedi. In gratitude Bim joined the Rebel Alliance and saw action on the forest moon of Endor, frozen Hoth and arid Tatooine. Upon his return to earth, with laurels upon his brow and feted as a war hero, he wanted nothing more than to return to nature and work the land; a simple agrarian lifestyle, far away from conflict. He kept a low profile and slipped from the public consciousness, his past largely forgotten and his true identity unknown to those few mortals who met him on his occasional forays into urban areas in search of cheap thrills and rice flour. He may have remained forgotten and unknown, wandering Southeast Asia as a vagabond, had he not overheard a conversation in a bar one night whilst on one of his jaunts into civilisation. A pair of businessmen were talking in hushed tones about a new disruptive force, sweeping all before it and trampling all over norms and customs the world over. No, this was not a US presidential candidate, but an American software developer called Autodesk, and in particular a product called Revit. Intrigued, Bim sought knowledge and found a ready source of pudgy, pallid and poorly dressed men from the damp isles of Britain; a cold and windswept outpost on the extreme fringes of Northern Europe. A destination even the all-conquering Roman legions decided to abandon due to its inhospitable climate, arcane traditions and warm beer. However, it turned out that living in fog and drizzle for three hundred days of the year also accelerated creativity and the ability to generate a seemingly endless number of Microsoft PowerPoint slideshows, as well as memes. Bim immediately felt comfortable in this land of sunlight starved and sexually repressed Gollums, and within a short time he had established himself as a purveyor of some of the finest slideshows, Yammer posts and memes. Bim travelled the world, expounding eager audiences with tales of 15-20% efficiency gains, whilst providing little or no hard evidence. It was like a dream come true for Bim, having felt that he had discovered his true calling! The rise of Bim has since been vertiginous, with almost all nations, states, principalities and fiefdoms seeing the benefits Bim brought, but with one stubborn exception; Hong Kong. Seeing it as almost his divine duty, Bim took it upon himself to conquer that semi-submerged volcanic caldera in the South China Sea. He has been there ever since. Hong Kong still stubbornly refuses to accept Bim, yet still he persists. Now entering the third decade of his second century of existence, he feels sufficiently knowledgeable to be able to pass on some of his experiences, here in this blog. Read on, brave adventurer!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.