A vaccine, a car and an Excel spreadsheet meet in a bar...

Fri, 04 Jun 2021 - Gertjan Filarski

Last Tuesday I was vaccinated with the Janssen vaccine. A single shot protects against COVID-19 in about 67% of the cases. On Wednesday the Dutch healthcare authorities stopped using Janssen. In very rare instances it may cause complications. Since the Netherlands has enough supplies, the health services now prefer to administer those.

And while I was sitting at a bar - for the first time in almost one and a half years - celebrating my vaccination, I again had to think about trust...

Why do I trust?

Trust is usually defined as an interpersonal relationship: one person is willing to rely on the future actions of another with usually limited control. I find this definition too narrow. I not only trust people - I also have a trust in objects, or even more generic: in systems. Of course objects and systems are designed and built by people. But I am too far removed and don't know them. I still trust the results though.

Take my car for example: I drive a Hyundai Tucson, but I don't know any Koreans. I rely on it blindly and everyday I push it to a (slightly illegal) 130 to 140 kilometers per hour. I trust it with my life and even the lives of my wife and children. Why?

Same for that Janssen-vaccine. Even though it was developed by a pharmaceutical company in my hometown, I don't know anyone in that industry. So why do I trust it? So much so that I now sit celebrating at a bar in the Springtime sun? I could not even wait to get it!

The usual answer people tend to give, is that you can place trust in systems when they have assessment processes and checks & balances. I think that is cheating. I don't take the time to check those, and it's not as if nothing is at stake! I simply trust that those systems and processes are in place and do what they are supposed to do.

Transparency

So what then? In the end I keep coming to the conclusion that trust and faith are almost the same thing - but not quite. I believe that there are enough good people involved to reduce the chance of terrible-catastrophes-happening. I lack the knowledge, time and resources to go and check every assessment, safety control and hiring process. And frankly it is a recipe for a very stressed and unhappy life to go doing that all the time.

The difference between trust and faith is that if I wanted to I could go and check. Maybe Hyundai would not give me access to their factories (and I wouldn't blame them) but I could learn enough car mechanics to assess the work my garage does. And I could gather the information to figure out how the bureaucracy checking garages functions. I don't and decide to spend my time differently, but if I wanted to, I could.

So in order for me to trust a system I need to know that it is transparent. That knowledgable people can review it - a strong and independent investigative press for example.

Trust in Software

Which brings me to software development and Excel sheets. A subject that I do claim some knowledge about. What makes me trust the results of a software application? The answer should be the same: transparency. But how many systems and spreadsheets I build, truly consider transparency?

Unlike a car or vaccine, spreadsheets with financial forecasts are not a matter of life and death. But getting it wrong may have a serious impact. Why do we trust it? It is nothing but rows and rows of intransparent cells with formulas. A copied mistake (or an intentional change) can result in a business unit able to pay the bills or not.

I am not alone. Few people put effort in creating transparent software solutions. Some may build things that are "open source" and that certainly helps a bit. But an open source version of Excel won't magically turn user created spreadsheets more transparent. In my opinion we, as software developers, need to seriously reconsider how we develop software. Let's start making tools that help people to create more transparent content. When we do that we can't limit ourselves by only thinking about our immediate users - we must also consider their sources, their team, and their audience.

Take Excel for example: the user is the person who creates a spreadsheet, a team member may alter it again later, the data sources are often manifold (financial systems, research platforms, etc.), and the audience may be a management team or a board. As software developers we need to provide tools that do more than just showing the computed results of a mass of coded formulas. We need to provide tools - a new Excel if you will - that include integrated audit trails. A log of who changed and added what, where and when. An environment where people can view the original data and not only the current version stored in the sheet. Not to mention a platform that provides insight in the steps that led to calculated numbers. How can I rely on an extensive set of VLOOKUP and INDEX formulas combined with three or four (or five...) nested IF... THEN conditionals? Without reviewing the individual cells I can not trust that the answer is actually correct.

None of this technology is new. These features are part and parcel to the platforms that software engineers themselves use to build applications. To improve trust we should start adding these very same features to the daily tools that non-developers use to create their own content.

Can we help you?

Audits & Consultancy

An extra set of eyes to see if you are where you want to be, or going where you had imagined.

Grant Acquisition

Both editing and authoring of (EU) funding proposals.

Interim Management

Temporary assignments at home or abroad to get projects and teams up to speed - or back on the rails.