To code or not to code From coding to competence · ‘digital competence’ was coined to capture...

35
To code or not to code From coding to competence

Transcript of To code or not to code From coding to competence · ‘digital competence’ was coined to capture...

Page 1: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to codeFrom coding to competence

Page 2: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

02

Page 3: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

03

Introduction 06

Reframing the problem 08

A framework for digital competence 11

Student and worker attributes 14

Populating the model 18

Teaching digital competence 22

Measurement 25

Conclusions 27

Contacts 30

Endnotes 32

Contents

Page 4: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

04

Foreword

Digital technology is having a profound effect on the 21st century organisation. Driven by accelerated connectivity and cognitive technologies, the nature of work and the workforce is also changing rapidly. And as the workplace evolves through this augmentation of software, robots, crowds, and artificial intelligence, almost every job is being reinvented. Deloitte has been at the forefront of this trend, working with employers to navigate the future of work. Together with our clients, we are striving to understand the ‘new’ workforce and to define the changes we all must implement, from the way we define strategies and business models, to how we design jobs and organise work, to how we think about workforce and skills planning. The question that logically follows is this: How do we align education and training with future workforce requirements?

A growing body of research explores the drivers of this transformation and investigates how we best educate to keep pace with the changing needs of the workforce. We know on the one hand employees are now expected to have longer careers, yet on the other hand the average tenure of a job and the shelf life of a learned skill is decreasing. The need for employees to continuously develop is increasing with the corollary that access to education and skills development will become even more important. We also know that as digital technologies become more embedded in life and work, STEM will remain a top education priority1.

But technical skills will not be sufficient in themselves. In Deloitte’s paper on the The future of the workforce: Critical drivers and challenges,2 we predict that businesses will need employees with more skills including: digital know-how, management capability, creativity, entrepreneurship, and complex problem solving. This is not to say that we do not and will not need a larger stock of technical skills in the workforce – we do. But the key will be balance as technical skills are no longer sufficient in themselves.

This trend can be applied to digital tools. We are coming to the realisation that what is important is our ability to work effectively with digital tools, to collaborate with them, rather than the depth of our individual knowledge and skills, or that of the digital tool. This ability will determine how successful we will be. For example a human pathologist is 96 percent accurate at identifying breast cancer cells, AI-based techniques are 92 percent accurate (and rapidly catching up with humans), while humans and machines working together are 99.5 percent accurate.3

In 2016, Deloitte’s Australian Centre for the Edge team and Geelong Grammar School decided to turn their attention to coding and digital literacy. This included discussion on how and what we teach, primarily around the question: ‘To code or not to code?’ The first round of symposia held last year by the Centre for the Edge and Geelong Grammar School showed that the rush to teach everyone how to code was obscuring the possibly more important need to ensure that all students and workers are ‘digitally competent’, comfortably integrating digital technology into their work.

Teaching everyone how to code cannot address this problem. The first round of symposia highlighted the need for all students to undertake a compulsory introduction to coding course, primarily to demystify digital technology. However, what’s more important is knowing when and why to use it. It’s this when and why that we need to focus on if we want all students and workers to be digitally competent.

The Centre for the Edge and Geelong Grammar School are building on the success of that first round of symposia, through this essay that develops the idea of ‘digital competence’, and through a second series of symposia. The digital competence framework described in this paper has been developed with a premise of linking the demands of the worker and the workplace directly to how these attributes might be taught – and at all stages of the learning continuum from the early years to learning later in life. It recognises that the challenge of adapting education to the emerging environment is not something that students, teachers, parents or industry can do on their own.

I would like to thank the broad range of participants who have contributed their time, experience, and opinions to the symposiums, and to Geelong Grammar School for the opportunity to be part of an exciting and unique collaboration. It is the contributions of these participants that enhance our collective capacity to act. And in this digital age, the pace and thoughtfulness with which we act together is what will determine our future.

Colette RogersPartnerNational Leader, Education Deloitte

Page 5: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

05

All learning happens within contexts. The rapid rise of technology and the digital world has seen the context of work change significantly. This fluidly evolving landscape is not confined to a few sectors of the economy. Across the world society as a whole is being disrupted by technological change.

It was clear in the first round of symposia held by Deloitte’s Centre for the Edge and Geelong Grammar School last year that this is true of work in Australia. It is therefore essential that the field of education not only recognises that the world has changed, but adapts accordingly.

In many fields of endeavour, employers have historically had a close relationship with the training providers who supply their generations of workers. As the needs of a profession change, so must the education of the workforce. In recent years, fields such as medical education have significantly changed not only their curricula, but their fundamental pedagogies, to produce graduates who can meet the demands of occupations in rapid transition.

As technology now influences all sections of society, it is insufficient for individual professions or organisations to attempt to upskill their workforce in all aspects of the new digital landscape. A more considered, systemic response is required.

Unfortunately, the velocity of the digital revolution is colliding with the lethargy of effective change at a government and policy level. Around the world, governments and education departments are calling for generic, but ultimately short-term responses, crying out for creative and innovative digital citizens who can change the world through start-ups, yet not addressing the fundamental underpinnings needed to support this new paradigm.

Last year’s round-table discussions between the stakeholders from a range of sectors identified that the future looks hopeful. What evolved from each meeting was a sense that there is in fact much common ground to be found. It appears that, although educational practice needs to adapt, there is a broad range of skills and attitudes, which, if introduced and implemented across the education sector, could assist our students in becoming literate and skilled in a new way. Technology is not mysterious, it is a set of skills that we need to manage from both a practical and philosophic perspective. We do not need to wait for policy makers to act – employers and educators can communicate, clarify, collaborate and implement change through forums such as these.

We believe that by identifying the range of skills and competencies required, education providers can meet the challenges of change in an informed way. Teachers’ professional learning and development can consistently focus on skills development, rather than merely knowledge acquisition in a subject area. This new focus can then be passed on to our students in the classroom through innovative and creative pedagogies.

As such, it is with a great sense of optimism that I look forward to the next round of symposia. Collaboration is seen as a key skill for our fluid times. The relationship between Deloitte’s Centre for the Edge, Geelong Grammar School, and our colleagues in the independent and public, employment and education sectors, is a meaningful and purposeful demonstration of proactive collaboration in action.

Rebecca CodyPrincipalGeelong Grammar School

Foreword

Page 6: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

06

Introduction

Page 7: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

07

‘Everyone should learn how to code’ has become a call to action across the community. Significant resources are being devoted to teaching primary and secondary students how to code and there are even calls to make computer science a secondary graduation requirement.4,5 Despite all this activity there doesn’t appear to be a common definition of ‘learn to code’ that everyone works from. The phrase refers to different things in different contexts from different stakeholders. The national conversation on coding in the curriculum seems to have leapt directly from idea to implementation, bypassing analysis or the formation of a reasoned approach.

In 2016 we hosted a series of roundtables to open up the debate, unpacking how different stakeholders (educators, students, parents, and industry) interpreted ‘everyone should learn how to code’, and explore the differences.6 It was clear that stakeholders had a range of equally valid but differing concerns, and were using ‘learn to code’ as shorthand for these concerns. The series concluded by providing a single, simple, unifying definition for ‘everyone should learn how to code’:

The incorporation of digital technology into one’s pursuit of work.7

where ‘work’ is defined broadly as “any activity in pursuit of an outcome” and can include hobbies and pastimes just as much as paid employment. The phrase ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy and digital citizenship. The roundtables made it clear that coding was only the tip of the iceberg, and that the community was more concerned about digital competence. Indeed, rather than coding, the focus should be on fostering a broad range of skills, such as computational and critical thinking, discernment and even creativity in students, and helping students to connect these skills to their work with digital technology, endowing them with digital competence.

It is not possible, though, to teach to such a broad definition, so while the roundtables provided insight, more work is required. We need to unpack what we mean by digital competence and enumerate how our new relationship with these digital tools is changing the nature of work, and the demands on the worker and workplace,8 and create a framework to help us answer the question: how do we prepare students for a life immersed in this emerging digital environment? The framework needs to capture the relationship between the digital tools and the worker and be populated with the attributes required of them: capabilities (knowledge and skill) and predilections (attitudes and behaviours). We also need to identify a set of examples that demonstrate how these attributes might be taught. Together – the framework, the attributes it organises, and the examples – can provide us with the foundation of an inclusive definition of functional digital competence for education (K-12 through tertiary) and training (post-secondary and industry learning and development).

Page 8: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

08

Reframing the problem

Page 9: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

09

The debate on the future of work has been framed in terms of creating or using tools. Our relationship with technology has been shaped by this dichotomy since the dawn of the industrial revolution: technology realised as tool, with worker as tool maker or tool user. One consequence of this is the common assumption that if we can create digital tools to automate all tasks in the production process, which we appear to be close to achieving, then workers will need to focus on making digital tools (‘coding’) as there won’t be opportunities for anyone using digital tools per se.9 Or, put another way, the incremental automation of more and more complex tasks, and the development of ever more capable autonomous technology, is pushing many workers out of tool user leaving tool maker as their only option, should they want to be employed.10 If the future is to be dominated by digital tools, then the only work available for humans may be making those tools, coding. There is also a general fear that not everyone, or at least many people, will be capable of learning to code and developing the new digital tools. This is one of the drivers behind calls for a Universal Basic Income.11

Digital tools come in two general types. First, there are the simple instrumental tools, such as calculators, that we use. We might consider these ‘tools that contain digital technology’ rather than ‘digital tools’. These are similar in nature to mechanical tools, such as a hammer or abacus. Second, there are more complex, algorithmic digital tools that we use to capture decisions and decision-making processes, which are not fully formed when sold and must be adapted to the task at hand. Spreadsheets are an obvious example. This second group of tools is different from previous automation technologies, as the tools are both more malleable and more opaque. Consider how a spreadsheet requires a financial model to be created within the tool before it can be used to solve a problem.12 This second group of tools have higher literacy and numeracy requirements, as we interact with them through language. Therefore, we note that one of the obvious implications of a digital future is higher literacy and numeracy requirements for workers than in the past.

Incorporating digital tools into our work forces us to understand the models these tools contain and adapt the models to our needs. This might be detailing a financial plan via a spreadsheet, where the spreadsheet has a particular approach to representing financial information that we must adhere to. Or it might be more complex, such as the end-to-end voting process and not just the voting algorithm. These resulting systems should also be considered imperfect, as while they can leverage the benefits of digital technology, they are also constrained by the technology’s limitations and are at best only approximations of the physical or social phenomenon we are trying to represent. George Box, a statistician, captured this nicely with the aphorism “all models are wrong but some are useful”.13 It’s important for workers to understand that all digital systems work with approximations and will, consequently, contain errors, make mistakes, and subsequently may behave in strange and unexpected ways.

Page 10: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

10

Our relationship with these digital tools goes beyond the simple tool maker, tool user relationships of the past.14 By casting decisions in formal language and then embodying this language in autonomous ‘bots’ that interact with the world through a narrow set of sensors & effectors15 and a particular approach to reasoning, we are endowing them with a degree of autonomy and agency. An extreme example of this being programming a semi-autonomous military drone to seek and destroy targets based on a predefined sensor profile, though we can see a limited version of this in things like Centrelink’s recent robo-debt challenge.16 We don’t relate to these tools as inanimate objects as their agency affects our own, hence our relationship with technology is clearly evolving.

“If we want to unify the perspectives on what ‘learn to code’ means then we need to reframe the question and move away from this dichotomy of tool maker and tool user to embrace the new relationships that are emerging.”

If we want to unify the perspectives on what ‘learn to code’ means then we need to reframe the question and move away from this dichotomy of tool maker and tool user to embrace the new relationships that are emerging. Individuals who are unable to embrace these new relationships could find themselves disenfranchised due to the lack of critical thinking and discernment skills required to understand and engage with a world where digital tools are granted some autonomy and agency.

They could also potentially be open to manipulation from those who have a better understanding and control of the technology and its use. This is particularly topical now after the recent revelations of Cambridge Analytica.17

Page 11: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

11

A framework for digital competence

Page 12: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

12

Our target is not an existing domain or profession, so we can’t use the typical approach of deriving our framework from a survey, asking experts what should be taught. The broad scope of our task also prevents us from integrating established frameworks, such as digital literacy, computational and design thinking, etc., to create a new, unifying framework. Instead we need to build a framework that integrates the different perspectives and helps us tease out what’s required.

The foundation for our framework is the realisation that many of these new algorithmic digital tools are relational. We’re delegating decisions and reasoning to these new digital tools, providing them with a limited degree of autonomy and agency in the process; a limited degree of autonomy as we’re allowing them to make particular decisions in specific ways, and a correspondingly limited degree of agency as they can only choose from a set of predetermined actions. This autonomy and agency, though limited, enables them to take on roles in the organisation chart, as manager, subordinate, or co-worker; which is in contrast to the earlier instrumental technologies.

Workers18 are increasingly finding themselves working for a machine (as ride-sharing drivers do), working with a machine (the common meme of AI augmenting a worker), or working on a machine (such as when a worker commands a fleet of ‘bots’). In some instances, human leads machine, in others machine leads human, while in some cases human and machine may also collaborate. The reverse is also true, where machines are working with, for or on human workers, and must be designed to function in these roles. We must also consider instances where worker and digital tool are equals, as well as instances when the human takes the lead in the relationship versus when the machine takes the lead. This can be represented in a three-by-three matrix, nine cells describing the new ways we relate to technology and what work will look like in each instance.

If we enumerate the attributes required of a worker in each cell then we can determine what it means to be digitally competent in a particular job.

Page 13: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

13

Figure 1: Our relationship with digital technology

... work for... ... work with... ... work on...

Hum

ans.

.. M

achi

ne

DirectionA human working under the direction of a machine, with the machine assigning work and assessing the quality of the product. Ride sharing driver, pick-n-pack in a distribution centre.

Machine augmentationA human monitors a machine’s operation, stepping in when the machine is out of its depth and about to make a mistake. A ‘driver’ monitoring an autonomous vehicle, or an algorithm for bias and compliance with the law.

InstructionA human teaches an old dog new tricks. E.g. an engineer formalises best practice for the design and certification for a home design tool, a ‘truck driver’ teaching autonomous trucks to park at a new distribution centre, or teaching a smart home to maintain a preferred temperature.

Mac

hine

lead

s

Colla

bora

tive

Shared agency, negotiationHuman and machine with dependant responsibilities forced to negotiate. A district nurse managing their time and work management system assigning new work.

SynthesisHuman and machine collaborate to identify and solve a problem. Superannuation, with a financial model of the client’s retirement as the focus, the human working with the client to discover their ‘happy retirement’ and the robo-advisor exploring different investment scenarios.

BricolageHuman and machine behaviours are integrated to create a new solution. Overcoming ‘learned helplessness’ by extending digital literacy to provide students with the behaviours required to discover how digital tools might be bricolaged to solve a problem.

Mac

hine

s...

hum

ans

ShepherdingA team of machines working for a human, where the human assigns work and assess the result. A trader managing a team of trading ‘bots’ that control investment portfolios, setting and updating the ‘bots’ objectives and intermittently monitoring their progress.

Human augmentationA machine monitors a human’s work, stepping into highlight potential issues and problems. A ‘sentencing computer’ monitors a judge’s deliberations to help the judge avoid bias in decisions.

GuidanceA machine helps an old dog learn new tricks. A Fitbit prompts its owner to help them reach their well-being goals, or a self-paced learning solution tailors a MOOC to an individual student’s abilities and progression through the course.

Hum

an le

ads

Figure 2: Our evolving relationship with technology

Technique

Create tool

Work on machines

Work with machines

Work for machines

Use tool

Craft Technique Algorithmic

Note that we’re not proposing these new relationships replace the old tool maker and tool user ones: all exist simultaneously. For example, while we’re not focusing on programming – a tool maker versus tool user relationship – programmers will clearly still exist, though they will be more specialised. Similarly, the original craftsperson relationship, where tool maker and user are the same, still exists today. There are actually three frameworks at play at once: craft (craftsperson); technique (tool maker and user), and algorithmic (work with, on and for). The challenge is that for much of the population the emphasis has shifted from craft to make and use, and now appears to be shifting to work on, with, and for.

Page 14: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

14

Student and worker attributes

Page 15: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

15

The question is then: what do the cells of our framework contain? Using a populated framework, we can define what we mean by “Learn to code”, where ‘competence’ is a binary attribute: i.e. competence is merely having the attributes required to productively engage in some of these relationships in a suitable context.

At the most fundamental we need to consider a student’s literacy and numeracy. Language is the primary means of interacting with algorithms, with the language becoming increasingly formal the closer we get to the machine. Indeed, computer programming can be seen as a branch of applied mathematics, as it involves describing a problem in excruciating detail so what is to be done is clear to the computer. Though few workers will be required to ‘programme’, as the activity is commonly imagined, their interactions with these digital tools will be dominated by language and numeracy. Consequently, we need to ask ourselves what the literacy and numeracy requirements are in each cell of our three-by-three.

Consider ride-sharing drivers, where a human is working for a machine (top left of our three-by-three), with an algorithm allocating the work and measuring worker performance. The worker needs to understand the factors that shape the machine’s decisions, as they do with a human manager, if they are to understand why particular pieces of work were allocated to them, and how their (measured) behaviour will affect their rating i.e. how the computer will use a measurement to determine the new value. They need to be able to discern the reasons behind these digital interactions, reasons generated by humans, as decisions, such as ratings, are human in nature. A financial worker in this world – such as a superannuation advisor – will have even more stringent numeracy and literacy requirements. Here a human and machine collaborate, working together to simultaneously build a financial model and solution for a client. The superannuation advisor collaborating with the machine needs to express their thoughts in language the machine can consume.

This doesn’t require them to programme the machine, but they do need to be able to express themselves using domain concepts that they have in common with the machine, and to understand how its inputs map to outputs, increasing the minimum requirement to functional literacy. As with our ride sharing driver, the worker must understand the factors driving the machine’s decisions and actions, though in this instance the worker may require a deeper understanding as the machine will be manipulating a shared model, rather executing an unchanging algorithm.

Page 16: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

16

Workers will also require superior metacognition than is typical today. Consider the current concern about biases in AI. All reasoning systems have biases, both human and machine, as these are a direct consequence of them being physical things: their connection to the world is limited by their sensors and effectors, and their ability to deliberate constrained by the available time and energy. In a noisy and confusing world, we, both machines and humans, rely on cribs – shortcuts and assumptions – to make our task easier.19 These cribs can be quite simple. For example, a classification algorithm that identifies military tanks might have been trained with a set of images where the tanks were all presented on a lush green lawn outside the garage where they are kept. The classifier, being no slouch, deduced that “tanks are things sitting on lush green lawns” and proceed to identify anything resting on such a lawn as a tank, regardless of any obvious physical differences between a tank and the thing on the lawn. A subtler version of this is the assumption many autonomous cars make that any large panel that suddenly appears in front of them is an overhead road sign. The car’s developers might do this as it is difficult to discern what such a panel is with that car’s limited sensors, and instruct (configure) the car to ignore such things as they are most likely overhead signs. This breaks down though, when a vehicle in front suddenly swerves to reveal a stationary emergency vehicle (to be avoided), though the car assumes that it’s an overhead sign (and can be ignored). This shortcut was behind a recent crash.20

Improved standards in literacy and numeracy are required to enable workers to understand the decisions a machine makes, while superior metacognition is required for the human to understand the limits of a machine’s reasoning, and how that reasoning will affect their own.

Capabilities enable us to use digital tools to intentionally change the world around us. Digital literacy, for example, encompasses the knowledge and skills required to use a range of common digital tools, how to navigate a graphical interface or compose an email or text message. Digital citizenship is a larger concept, encompassing digital literacy, and includes the capabilities required to use digital technology as a media to engage with society, typically defined as “those who use the Internet regularly and effectively”.22 Previous work in developing curricula for digital technology is also clearly relevant, as it enables students to “design, create, manage and evaluate sustainable and innovative digital solutions to meet and redefine current and future needs”.23

Predilections, on the other hand, determine how we engage with the work, the others that we are working with (both human and machine), and the context within which the work is to be done. As we move into an era of digital decision making, we must consider not just how workers use (digital) tools, but how they engage with these algorithmic digital tools.

Attitudes are something like the ‘habits of the mind’24 that have been developed for mathematics, science, and engineering. Attitudes determine how the worker approaches the work: do they focus on the parts of the problem or the whole, do they consider visualising the problem, do they attempt to adapt existing components, and so on.25 These attitudes are teachable and are an important part of enabling workers to overcome the ‘learned helplessness’ that many suffer from when dealing with digital solutions,26 and should be an integral part of a digital competencies curriculum.

Humans can integrate a greater variety of information into their decisions than machines, as our ability to notice the unusual and make sense of the world provides us with a richer connection to the environment. Machines, on the other hand, are restricted to the limited set of sensors and effectors they are engineered with. At a basic level this is the ‘tank on the lawn’ problem, at higher issues it contributes to the challenge of distinguishing ‘fake news’ from real.

This is not a technology problem, as humans suffer from taking thinking shortcuts as much as machines. What is different is the increased volume of ‘decisioning’, both in human and machine, we see today, as well as the potential for the consequences (both bad and good) to be rapidly amplified by automated machine ‘decisioning’. An erroneous data point, for example, might change an individual’s eligibility score sufficiently that badly needed support services are automatically withdrawn. Automating these decisions improves productivity, but it also raises the stakes.

Finally, we need to consider the abilities the worker requires. Clearly these will include capabilities: knowledge and skills that we use to intentionally engage with the world. However, we should also consider them as containing a worker’s predilections21: attitudes and behaviours that shape how they react to the world around them, and other actors in this world.

Page 17: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

17

Behaviours, on the other hand, determine how they will respond to stimulus. Creativity provides us with a simple example.27 A team might see creativity as a good thing, something to be encouraged; an attitude. Then, toward the end of a meeting, one of the team members throws out a seemingly random (though potentially creative) answer to a question. How one behaves in response to this stimulus might determine if this is an opportunity for a creative step forward, or a distraction. The team could brush the response aside and move on to close the meeting as time is short. They might agree to an open-ended exploration of the idea, extending the meeting, potentially indefinitely. Or they might decide to allow the meeting to run a little over to provide time to explore how the response is connected to the initial proposition. Which is the most appropriate behaviour will be determined by the context. Creativity, as with “everyone should learn how to code”, is a term full of implicit and erroneous bias, often framed in terms of one’s natural ability. It is more productive to frame both creativity and digital competence as a set of predilections, a teachable collection of attitudes and behaviours.

This highlights the relational nature of each cell in our framework. While each cell will contain capabilities – one’s ability to intentionally use technology – it also contains predilections – how one approaches the work, other workers (both digital and not), and the context – and how one responds to their autonomy and agency, even though both are limited.

Page 18: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

18

Populating the model

Page 19: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

19

For our model of digital competence to be useful we need to populate the cells of our competence framework.

We must acknowledge, however, that the domain of work is important. One isn’t ‘digitally competent’, for example, one is a ‘competent digital citizen’. Competency requires us to note what domain and the context, that the individual is competent in. This means that competency will be different for a truck driver than a judge, a judge than a lawyer working on the prosecution, and different for different lawyers on the prosecution team.

As with creativity, competency can only be learnt and judged in context. It’s not enough to be taught how to use an internet search engine, students need to make the connection with the opportunities where an internet search engine might help them. “[K]nowing the technology is important, but knowing when and why to use it is more important.”28 Learned helplessness is a consequence of this. In the roundtables in the previous project, this was known as the ‘beer problem’ as one participant observed “Most employees can solve practical problems in the workplace, such as needing beer and snacks for Friday afternoon drinks – if I give them fifty dollars they can find beer and snacks. However, if there is a digital technology problem, even a basic problem with their device, they cannot solve the problem unless there is an app for it.” 29

The employees’ default behaviour is often to feign helplessness and ask to be taught when confronted by a digital tool they don’t know. One solution is to provide them with a richer set of behaviours, a simple example of which is typing the name of the application they are using into an internet search engine, along with a short statement of what they’re trying to achieve. While they might have been taught how to construct queries for a search – the skill in using a particular tool – this is different from developing the attitudes and behaviours that will help them to integrate it into their work. These attitudes and behaviours can be taught sequentially throughout schooling and into tertiary and the workforce as the worker becomes more sophisticated. It’s worth noting here that predilections are not particular to digital domains, as creativity, resilience, perseverance, and problem-solving skills have always been needed, though now we have a new context with the digital space.

So rather than attempting to populate a single model of digital competence, we need to understand how competency manifests in different professions and domains.

Page 20: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

20

Figure 3: Digital competence map

Domain knowledge

Literacy, numeracy and digital literacy

Critical thinking and discernment

Craft Technique

Machine leads

CollaborativeH

uman leads

Algorithmic

... work for... ... work with...

Assembly Synthesis Bricolage

ShepherdingHuman

augmentationGuidance

DirectionMachine

augmentationInstruction

... work on...

Consider the idea of digital citizenship, mentioned earlier. Digital citizenship is typically broken down over nine aspects: access to digital services; using online commerce; communication via digital platforms and media; digital literacy (using devices); etiquette in digital forums; understanding law online; rights and responsibilities; health, physical and psychological wellbeing online; and security and self protection.30 This concept is centred on the use of technology, absent are emerging challenges such as the increasing use of algorithms to score citizens and determine what government and financial services they can access; citizens unable to understand how they are being measured and how these measurements determine their access to services will find themselves confused and unable to find and obtain the services they need. We can recast digital citizenship into our framework to understand what the attributes of a digitally competent citizen might be. To do this we have integrated figure 1 and figure 2 to create what we might call a digital competence map, shown in figure 3.

Page 21: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

21

Starting from the left we have craft, the worker attributes that are directly related to the domain, mastery of domain concepts and their relationships. For a citizen, craft contains the attributes of the public sphere: an understanding of polite behaviour, of how society works and the function of government and of a citizen’s rights and responsibilities, knowledge of the electoral processes, and so on, all of which is covered extensively in Civics and Citizenship in the Australian Curriculum.31

Next, moving right, we have technique, where the knowledge and skills of the tool user live. For our digital citizen this includes the literacy and numeracy required to communicate with digital services and via digital platforms, along with knowledge and skills required to use the digital devices that are the gateway to the digital world, such as personal computers, smartphones and tablets. It contains the metacognitive skills – critical thinking and discernment – required to understand their interactions with these services, and the services’ responses. An example might be the challenge of determining what is ‘fake news’, and what is not.

Finally, on the right, we have the algorithmic section where decisions have been captured in algorithms and automated. We might consider a competent digital citizen, for example, to be someone who is not intimidated by digital technology (an attitude) and who, when confronted with digital tool or service they don’t know, can draw on a rich set of behaviours to discover how to apply it to their current problem. Alternately, they might require an appreciation of the algorithms that are used to rate them, and which control their access to government provided services, or even the credit score that determines their access to loans, along with a set of behaviours that will enable them to effectively manage their ratings. It’s important to note the distinction made here between the knowledge and skills associated with techniques, and attitudes and behaviours associated with algorithms. Understanding how to construct a query for an internet search engine to answer a particular question (knowledge and skill) is different from and distinct from a student realising that a search engine might be a useful tool and synthesising the question which forms the basis of the query (attitude and behaviour).

Our framework makes an important distinction between the worker attributes required by the domain they are working in, which lives in craft, and the attributes required to engage with the digital tools used in that domain, which live in technique and algorithms. It’s productive to consider the possibility of a digitally competent computer programmer; where a programmer is someone who has mastered the knowledge and skills associated with programming as an activity (possibly the creation of small website businesses), while a digitally competent programmer is a programmer who can effectively navigate the networked and digital environment within which much modern programming takes place.

“We might consider a competent digital citizen, for example, to be someone who is not intimidated by digital technology (an attitude) and who, when confronted with digital tool or service they don’t know, can draw on a rich set of behaviours to discover how to apply it to their current problem.”

Page 22: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

22

Teaching digital competence

Page 23: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

23

“Our goal when teaching digital competence is to help students understand how a digital solution is different from a non-digital one, the relative merits of each, and how the limited autonomy and agency of many digital solutions affects their own autonomy and agency, as well as that of others interacting with the solution. Students need to be sensitive to the benefits and limitations of digital technology, and they need the language to think about and discuss it with their peers.”

Our goal when teaching digital competence is to help students understand how a digital solution is different from a non-digital one, the relative merits of each, and how the limited autonomy and agency of many digital solutions affects their own autonomy and agency, as well as that of others interacting with the solution. Students need to be sensitive to the benefits and limitations of digital technology, and they need the language to think about and discuss it with their peers. They also need opportunities to bricolage a solution integrating digital and non-digital components and explore the benefits of both machine augmentation and human augmentation.

In terms of our competence model we’re working within a domain that matters to the students, providing them with a task where they can explore and improve their capabilities within the domain as well as their capabilities with the digital tools appropriate to the domain, while engineering the task (the ‘work’) and the context it sits within (the lesson, or ‘workplace’) to foster the development of appropriate attitudes and behaviours.

Educators will need a rubric or continuum to help them distinguish between levels of competence in their students. It’s important to note, though, that we’re not trying to imbue students with specific attitudes and behaviours, our focus is on students adopting (or developing) attitudes and behaviours appropriate to themselves. This requires us to embrace a system-centred (rather than technology centred) approach.

Consider the classroom exercise of creating a voting system, a common part of a digital technologies curriculum. There’s likely to be a discussion on the local electoral system and voting algorithm, and the relative merits of different algorithms. Then discussion will turn to design: the challenge of ensuring an accurate vote, potential issues with the current paper ballot system – the time taken for a manual count, human fallibility and the potential for mistakes, tampering, and even the challenge of interpreting poorly marked votes (‘hanging chads’)32 – and how the superior capacity and precision of computers might address these issues. Finally, the class will divide into groups where they implement the voting algorithm in a programming language, and then test their implementation against sample data sets. Due to the magic of digital technology the students believe that they will have created a faster, more convenient and efficient voting system, though in embryonic form, and wonder why we haven’t moved to digital voting already.

Unfortunately, framing an exploration of digital technology this way is problematic as it ignores the failings and limitations of the technology. We’ve confused digital competence with the aspiration that ‘everyone should learn how to code’. All algorithms must be embodied as part of a digital system before they can be used. In the case of voting we need to consider not just the implementation of the algorithm, but also how votes are captured to ensure that they accurately represent voters’ intentions, how votes are securely transmitted to the central tally location, how to detect miscounts should our implementation of the algorithm have bugs or if there were problems with data collection (including the potential for the voting system to be ‘hacked’), and the processes that will be used to reconcile any problems should they be detected. It’s the difficulty of addressing these system-level challenges, outside of the voting algorithm, that causes experts in online voting to consider a manual paper ballot to be the gold standard in accuracy and trustworthiness.33,34

Page 24: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

24

To adopt a digital competence-led approach we need to reframe the lesson, taking a more expansive approach that considers not just the voting algorithm, but also how the algorithm is embodied in an end-to-end system and how different individuals will interact with it. As educators we must consider: What are the digital competencies students need to make a case for or against digital voting? What competencies will they need to simulate and explore the end-to-end voting process? And are there any other complimentary competencies, such as research skills, critical thinking, choices in formats of presentation, that the students will require?

A digital competence-led approach might start by building their domain knowledge to establish the context of work: what is voting, why do we vote, and what are some different types of votes, and what are the alternatives to voting. Particular attention might be given to the requirements of a good voting system, such as fairness, inclusiveness, transparency, accountability, and stability, including an investigation of some existing systems and a discussion of the relative merits of each.

Next the students sketch out the end-to-end voting process, where individual components could be implemented manually or with digital technology (Bricolage). Students might also use this as an opportunity to develop their (online) research and discernment skills, investigating the issues such as the challenge of accurately capturing voter intent or supporting a recount to validate a result,35 and using what they discover to inform the design of their voting system.

Then the students might create the paper forms and/or digital components required, and role play a vote. The choice of tools might be left up to the students, as a spreadsheet can be used to implement a voting algorithm just as well as a programming language when only a few votes are being cast.

At the conclusion of the exercise students can share any issues they identified and review their voting system. Did their efforts result in a good voting system? Where did digital technology help? And where did it create problems? How could the system affect each of the stakeholders? Could their grandparents vote? What did they learn about digital systems during this exercise? As educators should we reflect on the digital competencies students used to make a case for or against digital voting and to simulate the voting process? Are there any other competencies that would have been beneficial?

Our challenge, though, is to integrate ideas from digital competence into other non-digital subjects, and to do this across all educational strata. Ideally this would be a graduated approach, where a student’s digital competency increases as their experience in a domain increases.

Page 25: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

25

Measurement

Page 26: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

26

The final question we must turn to is measurement: how does an educator determine that a given student is digitally competent in the context of their classroom? To gauge competency we need to determine if the student’s capabilities and predilections enable them to productively engage with the set task. We also need to be able to do this across all the educational strata: from foundation through year ten to senior secondary, tertiary and post-secondary, as well as industry. Consequently, while competence is binary, we need to distinguish competence levels within each of the areas our framework enumerates: domain expertise; literacy, numeracy and metacognition of digital tool use; and the predilections in each of the cells in our three-by-three.

Literacy and numeracy are fairly straight forward to measure as they have established metrics and measurement mechanisms. Similarly, for digital literacy and other digital capabilities (knowledge and skills); with the Digital Technologies from the Australian curriculum providing a wealth of material and already supporting the concept of ‘exporting’ content from Digital Technologies and ‘importing’ it into other learning areas.

Critical thinking and discernment, along with the predilections (attitudes and behaviours) in the algorithmic section of our framework, are more challenging to measure as they are contextual attributes where a student’s abilities in a particular domain do not automatically transfer to another. As was mentioned earlier, knowing when and why to use technology is more important than knowing the technology itself, and this can only be learnt in context. These are also divergent abilities, where a student might use different strategies, different behaviours, to address a challenge, and there might be multiple possible answers, as opposed to convergent abilities where there is a single ‘correct’ technique. In this way, digital competence is similar to creativity, where students can use different processes that provide different results, while being equally creative. A case in point is the learned helplessness many students have when confronted with digital solutions that are unknown to them, mentioned previously. Students can overcome this by having a rich set of attitudes and behaviours that enable them to explore the challenge and find a solution, though the particular attitude and behaviour used is not necessarily important. Indeed, a student might need to explore several options before progress is made, and a student’s disposition might lead them to adopt different attitudes and behaviours to another’s. A student with a theoretical learning style reaches for the manual while another might ask Google, a third turns to YouTube, and a fourth reaches out to a colleague who they believe to be more knowledgeable.

A practical way forward is to identify a number of threads in each of these competency areas – critical thinking, discernment, and the cells of the three-by-three – and then, for each thread, identify levels of competence. We might, for example, create a thread ‘navigating digital tools’ that capture a worker’s competence in using digital tools and incorporating them into their work. At the lower levels this would be the knowledge and use of tools, working from simpler through to more complex tools. Upper levels would focus on situations when the available tools are insufficient, when it is not obvious how to accomplish a task with a tool, or when there is no obvious tool to support a particular task; the challenges of learned helplessness. Each level contains a description of what competence looks like, and sets of associated capabilities and predilections. Educators can then use this hierarchal structure of knowledge, skills, attitudes and behaviours to design assessments against.

This approach can also be extended to certifications and curricula. A course designed to produce digitally competent bankers i.e. a FinTech36 degree where graduates are expected to emerge with a firm grasp of both the domain, finance, and the application of digital technology to that domain, for example, would draw on the threads to describe the attributes (knowledge, capabilities and predilections) of the ideal graduate. Progression through the associated threads would be sequenced into the curriculum, with affected subjects reframed, as we did with the voting example in the previous section.37

Page 27: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

27

Conclusions

Page 28: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

28

Digital competence is different from digital literacy. Digital literacy is founded on an industrial era, instrumental, relationship with technology where we are either tool maker or tool user. Digital literacy is a measure of our ability to use digital tools: digital watches, calculators, tablets and even online services. Digital competence is also different from coding. Coding is the flip-side of this relationship, worker as tool maker, and the rush to teach everyone how to code is a reflex response to the assumption that the ever-increasing sophistication of digital tools mean that in most, if not all, tool users will be eliminated, forcing the next generation to become tool makers or be out of a job. Digital competence is the “incorporation of (digital) technology into one’s pursuit of work”, so it’s the work that’s important. Consequently, digital competence can only be meaningly defined in a particular context.

The current wave of digital technology is different to the previous generations of technology. The algorithmic solutions it enables are more malleable and opaque than prior solutions, blurring the line between tool maker and tool users, requiring higher levels of literacy and numeracy as a consequence. They can contain models of the world and can sense, decide and act somewhat autonomously. This limited degree of autonomy and agency means that we don’t relate to these tools as tool maker or tool user. The old bimodal relationship is splitting into three, where we might work for, with or on a digital solution. We also need to consider situations where the human takes the lead, where the digital solution takes the lead, and when the two collaborate.

Digital competence is then a student’s ability to work within this ternary relationship with digital solutions. It is the ability to effectively work with, or and on digital solutions. In this way it builds on earlier concepts like digital literacy as this new ternary relationship didn’t supplant the old binary one of tool maker and tool user, just as tool maker and tool user didn’t supplant the craftsperson: all three relationships are in effect simultaneously. Consequently, to be digitally competent one must be:

• Competent in one’s chosen domain

• A competent user of the tools appropriate to the domain, possessing the capabilities (knowledge and skills) required to effectively use these tools

• A competent co-worker with the digital systems appropriate to the domain, possessing predilections (attitudes and behaviours) that enable them to effectively work for, with, and on digital systems.

This layered definition highlights a key point, that digital competence is contextual: one isn’t digitally competent, as mentioned earlier, one is a competent digital citizen.

Page 29: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

29

The emergence of digital systems has made literacy and numeracy, and critical thinking and discernment more important. Workers will increasingly find themselves interacting with (somewhat) autonomous digital systems, and language and numbers are how we typically communicate with these systems. The minimum standard of literacy and numeracy must be higher if we don’t want some segments of society to be disenfranchised. A higher standard of critical thinking and discernment will also be required, so that workers can understand the reasons, generated by humans, behind the digital interactions. Decisions, such as ratings, are human in nature, and students need to understand these automated decisions and how they affect them. It’s not enough to be able to read instructions and trust the machine, you need to be able to discern the intent behind what the machine is telling you. Blindly trusting decisions one doesn’t understand, made by machines, will disenfranchise students.

We also need to demystify digital technology. A stopped watch should trigger its owner to get a new battery, rather than to buy a new watch as it has run out of ‘magic’. Students need to internalise a set of predilections that empower them to navigate this new relationship with technology. This expands the remit of educators beyond the capabilities that we have traditionally focused on.

Most importantly we need to realise that digital competence is something that needs to be taught, as it is not intuitive and we cannot rely on ‘digital natives’. There’s an overestimation that these things are being taught somewhere else, or that they don’t need to be taught at all. But they’re not, and they do. One needs to be taught how to use a calculator just as much as a nuclear reactor. These skills need to be explicit, taught, and applied with an increasing level of competency.

To support this we can build a model of digital competence – derived from our relationship with technology, from craftsperson through tool user to collaborating with a digital system – and populate it with the literacy and numeracy, and critical thinking and discernment, requirements, and the capabilities and predilections that a student might need. As digital competence is contextual this new learning must be embedded in existing subjects, rather than treating it as an isolated learning area. Educators need to expand the scope of the class beyond the core content to include the use of digital tools associated with the domain, and collaboration with digital systems. The structure of the competence model can provide them with guidance on how this tool use and collaboration might be realised in their subject – Is there an opportunity to explore synthesis in this unit? – while the capabilities and predilections are the raw material for student learning. Any commonalities – such as a compulsory introductory programming class designed to ensure that all students have some understanding of what ‘coding’ is – can be factored out and sequenced appropriately.

The next challenge is to begin populating the model, a large task in itself. Our first step toward this will be to conduct a national series of workshops to refine the digital competence model and explore what digital competence might look like across the curriculum. The intent is for this to be a very open process that spans all the educational strata so that we have a view of what digital competence might look like in primary, secondary, tertiary, and vocational and corporate training.

Feel free to contact either of the lead investigators (Peter Evans-Greenwood or Tim Patston) if you’d like to participate.

Page 30: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

30

Contacts

Page 31: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

31

Peter Evans-Greenwood

Deloitte Centre for the Edge550 Bourke StreetMelbourne Victoria [email protected]

Tim Patston

Geelong Grammar School50 Biddlecombe AvenueCorio Victoria [email protected]

Page 32: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

32

Endnotes

Page 33: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

33

1. ICF and Cedefop for the European Commission. (2015). EU skills panorama (2014) STEM skills analytical highlight, 1-5.

2. Schwartz, J et al. 2016, The future of the workforce: Critical drivers and challenges, Deloitte, <https://www2.deloitte.com/content/dam/Deloitte/global/Documents/HumanCapital/gx-hc-future- workforce.pdf>.

3. Wang, D et al. 2016, ‘Deep Learning for Identifying Metastatic Breast Cancer’, arXiv:1606.05718 [cs, q-bio], viewed 18 May 2018, <http://arxiv.org/abs/1606.05718>.

4. Sawchuk, S 2018, ‘Make Computer Science a Graduation Requirement, Says College Board’, Curriculum Matters, viewed 8 March 2018, <http://blogs.edweek.org/edweek/curriculum/2018/02/college_board_computer_science_graduation_requirement.html>.

5. Johnston, R 2018, ‘Wyoming passes forward-thinking computer science education bill’, EdScoop, viewed 22 March 2018, <https://edscoop.com/wyoming-passes-forward-thinking-computer-science-education-bill>.

6. The series of roundtables, a collaboration between Deloitte Centre for the Edge and the Geelong Grammar School, was documented in To code or not to code, is that the question? See Evans-Greenwood, P & Patstson, T 2017, To code or not to code, is that the question?, Deloitte Australia, <http://blog.deloitte.com.au/code-not-code-education-question/>.

7. The initial formulation of this phrase was “The integration of (digital) technology into one’s pursuit of work”. In this version we’ve replaced ‘integration’ with ‘incorporation’ as the latter seems to better capture the intent expressed in the roundtables.

8. In this report we use ‘work’, ‘worker’ and ‘workplace’ as general terms for “a thing someone wants to do”, “the someone doing the thing”, and “the context in which the thing is done”, respectively. The use of these terms does not imply paid employment, nor should it be assumed that a worker undertakes work to produce a product as a worker may be engaged with the process of work as much as the product it produces (as is the case in many creative endeavours).

9. This, of course, assumes that we perceive work, labour, as the manufacture of some product. Individuals engaged in creative enterprises such as writing music, literature or creating an artwork, will still use (and abuse) digital tools as a conduit for their creativity. As mentioned in the previous note, we consider ‘work’ to also include labour where the value is derived from the process, rather than the end product.

10. This might be the difference between a ‘writer’ constructing template narratives that a ‘news reporting robot’ uses to manufacture stories from sports or financial data, and a writer handcrafting the same stories.

11. A Universal Basic Income is a welfare regime in which all citizens of a country receive a regular and unconditional sum of money from the government. There is no requirement to work, or to look for work, in such a society.

12. One might consider this to be similar to a sheet of paper and pencil, though there are important differences. The paper & pencil provides the author complete freedom when creating their model. The spreadsheet, on the other hand, constrains the author as they can only use concepts (and therefore methodologies) supported by the spreadsheet’s features. To successfully use the spreadsheet the author must understand what they are trying to express and to be able to express it in a way that the spreadsheet can work with. The spreadsheet, while more powerful, is a more complex environment to work within, and requires its users to make concessions in how they think about and model a problem. Compare this to an abacus, a tool which also contains a (simple mathematical) model. The sheet of paper & pencil provides complete freedom, the spreadsheet provides some freedom, the abacus provides none.

13. George Box used the aphorism, “all models are wrong but some are useful” as the title of a section in a paper published in the proceedings of a 1978 statistics workshop. The relevant passage is as follows: “Now it would be very remarkable if any system existing in the real world could be exactly represented by any simple model. However, cunningly chosen parsimonious models often do provide remarkably useful approximations. For example, the law PV = RT relating pressure P, volume V and temperature T of an ‘ideal’ gas via a constant R is not exactly true for any real gas, but it frequently provides a useful approximation and furthermore its structure is informative since it springs from a physical view of the behavior of gas molecules. ¶ For such a model there is no need to ask the question ‘Is the model true?’. If ’truth’ is to be the ‘whole truth’ the answer must be ‘No’. The only question of interest is ‘Is the model illuminating and useful?’.” See Box, GEP 1979,‘Robustness in the Strategy of Scientific Model Building’, in RL Launer & GN Wilkinson (eds.), Robustness in Statistics, Academic Press, pp.201–236, viewed 21 March 2018, <https://www.sciencedirect.com/science/article/pii/B9780124381506500182>.

14. A fully developed version of this line of reasoning will be published in a forthcoming essay, tentatively titled “On our evolving relationship with technology”.

15. As sensors enable us to sense what’s happening around us, effectors enable us to affect change. You might see a coffee cup with your eyes and grasp it with your hand. Similarly, an autonomous car sees via a combination of video cameras and LIDAR, and can spin the driving wheels to move and turn the front wheels to steer.

16. Pett, H & Cosier, C 2017, ‘We’re all talking about Centrelink, but what is “robodebt” anyway?’, ABC News: Background Briefing, viewed 6 May 2018, <http://www.abc.net.au/news/2017-03-03/centrelink-debt-controversy-what-is-robodebt/8317764>.

17. While it is unclear how effective the techniques used by Cambridge Analytica are, the same techniques are endemic in the online advertising community. Students need to be equipped to understand what they are consenting too when providing personal information, and how this information may be used to attempt to influence their behaviour. For an overview of the Cambridge Analytica issue see Kaufman, M 2018, ‘Cambridge Analytica may go down in flames, but its practices won’t’, Mashable, viewed 28 March 2018, <https://mashable.com/2018/03/27/science-behind--psychographics-cambridge-analytica-facebook/>.

Page 34: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

To code or not to code | From coding to competence

34

18. … and students. As noted earlier, we’re using an inclusive definition of work that can easily include students (and as many parents can attest, many students consider school to be hard work).

19. The natural biases and limitations of human reasoning has been extensively documented, as has the fact that algorithms are inheriting some of these biases as the bias are encoded into data and rule sets used to configure these machines. Our human biases are simply the result of being human, and are the consequence of mental shortcuts taken to enable us to be effective in a complex and changing world where we have incomplete information and limited time and resource with which to reason. Any reasoning machine will also have bias as it too will be working with approximations of the natural world, though the biases will be different and it will ‘think’ differently.

20. Ferris, R & Kolodny, L 2018, Feds to investigate Tesla crash driver blamed on Autopilot, CNBC, viewed 19 February 2018, <https://www.cnbc.com/2018/01/23/tesla-on-autopilot-crashes-into-fire-truck-on-california-freeway.html>.

21. We’ve used ‘predilections’ to refer to the attitude-behaviour pair as it captures the “developed responses to experiences” concept that we wanted to include in the framework. At the core of concept is the belief that humans can have informed choice with how they engage with the world; both attitudes and behaviours are malleable and we can choose to change them. We also considered ‘biases’ but prefer predilections as the latter is more fluid and doesn’t have the emotional baggage of the former.

22. See Ohler, J 2010, Digital community, digital citizen, Corwin Press, Thousand Oaks, Calif.

23. Digital Technologies n.d., Australian Curriculum, viewed 9 March 2018, <https://www.australiancurriculum.edu.au/f-10-curriculum/technologies/digital-technologies/>.

24. Refer to Goldenberg, EP 1996, ‘“Habits of Mind” as an Organizer for the Curriculum’, Journal of Education, vol. 178, no. 1, pp. 13–34, viewed 8 February 2018, <http://journals.sagepub.com/doi/10.1177/002205749617800102> for a discussion of the rational and definition of ‘habits of the mind’.

25. Adapted from Figure 9. National Academy of Engineering 6 habits of mind in Lucas, B et al. 2014, Thinking like an engineer: implications for the education system: a report for the Royal Academy of Engineering Standing Committee for Education and Training.

26. The concept of learned helplessness when confronted by a digital solution was a common discussion point in the roundtables in the previous project.

27. This example paraphrases one provided by Prof. James C. Kaufman PhD in a public lecture on Teaching Creativity as a 21st Century Skill on the 19th of July 2017. See Kaufman, J.C. 2017, ‘Teaching Creativity as a 21st Century Skill’, Centre for the Edge (Australia), viewed 9 March 2018, <http://c4te.deloitte.com.au/post/160576315312/teaching-creativity-as-a-21st-century-skill>.

28. Kereluik, K et al. 2013, ‘What Knowledge Is of Most Worth: Teacher Knowledge for 21st Century Learning’, Journal of Digital Learning in Teacher Education, vol. 29, no. 4, pp. 127–140, viewed 20 March 2018, <https://eric.ed.gov/?id=EJ1010753>.

29. Evans-Greenwood, P & Patstson, T 2017, To code or not to code, is that the question?, Deloitte Australia, <http://blog.deloitte.com.au/code-not-code-education-question/>.

30. Nine Elements n.d., Digital Citizenship, viewed 9 March 2018, <http://digitalcitizenship.net/nine-elements.html>.

31. See Civics and Citizenship n.d., Australian Curriculum, viewed 9 March 2018, <https://www.australiancurriculum.edu.au/f-10-curriculum/humanities-and-social-sciences/civics-and-citizenship/>.

32. Levine, S 2008, ‘Hanging Chads: As the Florida Recount Implodes, the Supreme Court Decides Bush v. Gore’, US News & World Report, viewed 9 March 2018, <https://www.usnews.com/news/articles/2008/01/17/the-legacy-of-hanging-chads>.

33. Leovy, J 2017, ‘The Computer Scientist Who Prefers Paper’, The Atlantic, viewed 16 March 2018, <https://www.theatlantic.com/magazine/archive/2017/12/guardian-of-the-vote/544155/>.

34. Schneier, B 2018, ‘American elections are too easy to hack. We must take action now’, The Guardian, viewed 23 April 2018, <http://www.theguardian.com/commentisfree/2018/apr/18/american-elections-hack-bruce-scheier>.

35. The challenge with digital voting, as with many digital systems, comes from connecting the solution to the real world. With voting this manifests as the challenge of accurately capturing voter intent and ensuring that the voter has only cast one vote, while also ensuring that the vote is anonymous (preventing votes from being sold), all of which are system-level issues and not concerned with programming.

36. Fintech is a portmanteau of financial technology used to describe a new generation of technology-driven companies in the finance sector.

37. The challenge of identifying and calibrating a suitable set of threads across all competency areas in our framework will be addressed in the series of workshops intended to follow after this report.

Page 35: To code or not to code From coding to competence · ‘digital competence’ was coined to capture this concept and to distinguish it from related concepts such as digital literacy

This publication contains general information only, and none of Deloitte Touche Tohmatsu Limited, its member firms, or their related entities (collectively the “Deloitte Network”) is, by means of this publication, rendering professional advice or services. Before making any decision or taking any action that may affect your finances or your business, you should consult a qualified professional adviser. No entity in the Deloitte Network shall be responsible for any loss whatsoever sustained by any person who relies on this publication.

Deloitte refers to one or more of Deloitte Touche Tohmatsu Limited, a UK private company limited by guarantee, and its network of member firms, each of which is a legally separate and independent entity. Please see www.deloitte.com/au/about for a detailed description of the legal structure of Deloitte Touche Tohmatsu Limited and its member firms.

About DeloitteDeloitte provides audit, tax, consulting, and financial advisory services to public and private clients spanning multiple industries. With a globally connected network of member firms in more than 150 countries, Deloitte brings world-class capabilities and high-quality service to clients, delivering the insights they need to address their most complex business challenges. Deloitte’s approximately 244,000 professionals are committed to becoming the standard of excellence.

About Deloitte AustraliaIn Australia, the member firm is the Australian partnership of Deloitte Touche Tohmatsu. As one of Australia’s leading professional services firms. Deloitte Touche Tohmatsu and its affiliates provide audit, tax, consulting, and financial advisory services through approximately 7,000 people across the country. Focused on the creation of value and growth, and known as an employer of choice for innovative human resources programs, we are dedicated to helping our clients and our people excel. For more information, please visit our web site at www.deloitte.com.au.

Liability limited by a scheme approved under Professional Standards Legislation.

Member of Deloitte Touche Tohmatsu Limited.

© 2018 Deloitte Touche Tohmatsu.