Raising a digital native

My son, with a mere 18 months to his name, is scarily good at handling his mom's iPad and my Lumia. My conundrum is whether to encourage him stacking wooden blocks over playing with the iPad and take the shiny gadgets away from him, or let him play Baby DJ as much as he wants.

My hopes for his future certainly include more mental than physical labor, which implies that being a digital native is more useful than being a very good stacker of blocks. Character development, however, certainly requires that he gets his hands dirty with all kinds of physical things to learn about the power and limitations of being a man.

I wrote my first story 1991 on a Kaypro II with an eight inch green-on-black screen, technology from my birth year 1984. It was about a talking pen who helped an old writer overcome his writer's block. It led me to a lot of experimentation with the various bits of software and files in my dad's library of 5,25 inch soft 'floppies' and started a lifelong passion for all things digital.

My parents, bless them, made a visionary decision a year or so later: They got a modern IBM personal computer and a dial-up modem, and they let me and my siblings access the internet for a short time every day. Back then that meant hours of Microsoft Encarta and minutes of using AltaVista. When I was ten the son of a family friend introduced me to Turbo Pascal. It was the start of my career in IT to this day, and the best thing to happen to my young mind since learning to read in English.

My son is growing up in a world where computers and internet access are taken for granted,  his understanding of the technological underpinnings of his universe will be more conceptual than technical.
The way he deals with devices, apps and content he likes even before he knows how to speak leads me to believe he will be as much more fluent with the use of this technology than I ever was. His understanding is not about how the technology works, but how to use it in order to satisfy his needs.

So where do I step in and set the boundaries on his digital adventures? There is so much literature on parenting that arguments can be found for or against any policy. My goal is to raise a boy into a man, and these days that means he needs to be proficient in the use of software and services to get where he wants to go.

Character is more important than ability for life's tough moments and choices, and I find it hard to asses how that aspect of parenting is changed by living in a partly digital world. Right now I believe that I should always give him as much access to technology and connectivity as he can manage responsibly. Of course what that means in the day to day toddling about with my phone remains to be seen. I don't have all the answers, no parent does. Perhaps our kids will be able to Google it some day, although I suspect that Google will mean as much as AltaVista by then.

Such is the way of things, including, regrettably, the skill set that allows me to determine what my son can and cannot do. The odds are good he'll be blogging some day about  how his decrepit father gets lost in the world of sensory immersion feeds.

Turing's Secrets

Alan Turing is famous for being the father of modern computing, the author of computing's peskiest problem, and for being gay. The first made him famous, the second notorious among the Technorati, and the third got him fired, chemically castrated and may have driven him to suicide. There's a lesson here for the modern day internet and for all of us.

You see, Turing told a police officer about his boyfriend in the course of reporting a burglary. He believed the burglary was a crime that need to be persecuted and the truth about his boyfriend was just background information. That backfired rather spectacularly in the moral confines of mid 20th century England.

Computing is founded on theories of what is computable, and Turing laid a strong foundation with his eponymous Turing Machine, which models what kind of problems are computable and how. An upshot his theoretical framework is that when you add sufficient complexity to computing systems to get to work on complex problems, errors will occur that are neigh impossible to detect and resolve. We know and hate these errors as bugs. Basically we cannot make computers complex enough to be useful without a lot of bugs.

Bugs in software contribute to many evils, from a blue screen of death on your office computer to Air France flight 447 pancaking into the ocean because the autopilot's error message didn't contain any useful information for the pilots.

Bugs are also the source of vulnerabilities in software, vulnerabilities that can be exploited by malicious hackers, state agencies and clever pranksters. Vulnerabilities can and do reveal the secrets we artlessly entrust to our computers, much like Turing entrusted the fact of his gayness to a cop. There has been much ado about the Heartbleed vulnerability recently, one that impacts the integrity of 'secure' connections. It turns out that for a number of years this assumed integrity was, in fact, absent and an unknown number of supposedly secure connections were tapped.

You see, it's not about what is recorded or by whom. It's all just ones and zeroes that we pretend mean something real. The internet is the most epic story we ever told together. The problem is that we cannot control how others interpret our parts of that story. Virtual deeds have very real consequences, and we cannot predict what those consequences will be.

The moral confines of this age mean that it is okay to work online, play games online and look at naked adults online, but it's not okay to incite hatred or threaten someone online. But what of the next epoch? Russia, China the US and the EU are changing our world, right now, as you read this. What is okay today might be hugely embarrassing tomorrow, or even land you in jail.

There is a huge amount of mistrust against the state agencies who are surveying the internet, but not nearly enough. It's as if we can't make ourselves believe that our shared illusion is real enough to shatter lives, even though it does so on a daily basis. Our passwords are weak and often repeated. Kids post copies of their passports on social media instead of faxing it because they have no concept of how dangerous that is. People download or stream illegal copies of music and film even though they know they shouldn't. And people are going to jail, as the EU is proud to report. Sometimes fairly, oftentimes not so fairly. We just don't know if what we do today incurs penalties tomorrow.

Remember Turing. Turing the genius for his work on computing and his wartime work cracking Nazi code. Turing the innocent for not being more circumspect about his gayness. Turing the persecuted for his inhuman treatment at the hands of righteous moralists. Remember the lesson his story teaches, so we may avoid his misadventures.

To the Left

The first time I heard about Shift Left is when I read an IBM whitepaper on the optimization of tech support. It was amazing, obvious and, for most IT organizations, way ahead of it's time. It took two years before I had a customer asking for this concept, and it's an instant hit with every IT manager who hears of it.

The basic premise that support tickets become increasingly expensive if multiple and/or specialized parties are involved in resolving them. It is therefore advisable to optimize IT infrastructure and support in such a way that the bulk of incident tickets can be resolved quickly and cheaply. The following picture sums it up pretty well:

ShiftLeft - Picture by OGD ict-diensten, used with permission.

If you take, from left to right, IT infrastructure, end users, IT support, system administrators, and technical experts, you want the largest volume of tickets to be resolved mostly on the left, rather than on the right side. After all, when something fails the end user cannot work. If it's not automatically resolved of fixed by the user himself, he just has to wait around while the service desk starts burning time and money. When the service desk cannot resolve the issue, the more expensive system administrators get in gear and start billing, all the while leaving the end user unable to do part of his work. In short, the further 'right' the problem goes before it's resolved, the higher cost in time and money. Hence, the drive to 'Shift Left'.

There are a number of things a company can do to enable this shift left. First is very good knowledge management, where the service desk learns to perform as much of the system administrators job as possible without significant error rates. Secondly, the end user can gain knowledge of how to resolve common problems on their own by making a knowledge base and relying on community support, training for commonly used devices and applications, and digital literacy.
Both the service desk and the end user need to be assigned sufficient rights to resolve common problems on their own for these two measures to work. Thirdly, modern IT infrastructure can be configured to be highly fault-tolerant, and if you switch to cloud services the issue becomes moot and you only have to worry about internet access.

The purpose is to optimize for quantity. Back-end systems can fail over to each other. Users can find their own 'any key'. The service desk is well able to execute common changes and resolve issues on it's own, given proper guidance and training. Sysadmins would much rather hack away at a difficult issue once in a while instead of being inundated in relatively common and easy tickets. Ideally, the cost, volume and resolution time of tickets is greatly optimized.

Thankfully the technology like cloud services are evolving to give a seamless experience even if single components fail. Digital literacy is increasing quickly and end users are quite happy with devices and apps that are intuitive to use and manage without reliance on IT support. As more people use tablets, phones and purpose-built apps to do parts of their work, the IT department takes on the role of a facilitator rather than a break-fix oriented club of technicians.

* He/his has to serve for all genders here :)

Finding an IT service provider to love

One of the niceties about cloud computing and having digital natives in the workforce is that your IT department can mature from being a cog in your organization to a lever for success. Instead of just knowing all about the bits and bytes, the department needs to be at home in vendor management. Part of this new role is delivering and governing IT services with one or more outsourcing partners through increasingly relevant frameworks like SIAM and COBIT. The primary capability of the New IT Department™, however, is building great relationships.

The secret to a great marriage is seldom in the prenuptial agreement. Having a great spouse who complements your weaknesses and enhances your strengths can take you very far indeed, as evinced by the infamous Underwoods on Netflix[1]. Conducting a marriage on the basis of legal paperwork is a poor relationship at best. A shared vision and ambition, however, is an excellent basis.

Traditionally, outsourcing IT services is about trading money for certain capabilities that your business needs to do its thing. As IT is something that you notice primarily when it breaks down, lags or fails to do what you want, IT outsourcing contracts tend to be heavy on performance clauses. These are supposed to warrant that most of the stuff will work most of the time, and get fixed quickly if it does break. This approach to contracting is utilitarian, defensive and ultimately anathema to what outsourcing can enable your company to do.

The magic of great outsourcing is finding a partner with whom you add directly to each other’s brand value and culture. Finding the right partner is worth a lot of time and effort. If your business relies on localized, region-specific service to your customers, don’t outsource to a large centralized offshore IT service provider. How could that ever be a good match? If your employees often work from home, by all means get an IT partner that is willing to go out there and deliver the same kind of service at home they can expect in the office. Do you expect a lot of acquisitions to integrate? Find the service provided who specializes in on-boarding and integrating diverse IT capabilities into a common standard.

It’s not doable anymore to have the IT department serve all your current and future needs at a reasonable price, unless you are in that sector yourself. You need a partner. You might as well find the one you can love. Best Value Procurement is an approach to contracting that helps to form the basis for a more holistic relationship than one based purely of price and service levels.

---

[1] To be clear, I don’t condone or extend the parable to the very skewed moral compass of the Underwoods.