Skip to main content

The Case for Radically New IT Training

Terry Critchley

This blog presents the case for a radical new approach to basic information technology (IT) education. This conclusion is based on a study of courses and other forms of IT education which purport to cover IT "fundamentals." It is based on my own decades of IT experience and dogma-free research into current IT literature and media.

Information technology training occurs in numerous forms from computer science (CS) courses, as taught in schools and universities, to other eclectic ones and PC-oriented versions of the computing world. I maintain that these courses, especially CS ones, do not stack up to the needs of the fluid, modern IT as practiced in the workplace, especially the enterprise. My reasoning is as follows:

1. There is, and has been for over two decades, an IT skills shortage which is at its peak today (any day).

2. Practically the only source of CS skills are the schools and universities and, of the CS graduates, over half do not stay in the IT job they were hired for. CS is grossly understaffed with females and a survey I created for the CAS (computing at school) group unearthed major reasons for this female reluctance as: too geekish and theoretical, boring and needs great maths skills. Neither is true of the IT world I inhabited and which I observe and write about today.

3. CS and other curricula, many of which I have studied, do not match even the keywords which typify modern IT as practiced in the workplace. This can be shown by comparing any existing curriculum with the attached keyword list which typifies modern IT. This list has been verified as representative of modern IT by four of my peers in IT.

4. Fully 70% of IT projects fail in degrees from not quite what I wanted to total disaster. This failure rate applies to the more specific area of digital transformation and legacy modernization. In short, nearly every IT activity.

As a result, most businesses are reliant on computers (digital) in a range of ways from their being necessary for us to function to mission critical. This reliance is badly hampered by the drawbacks in skills available, as discussed above.

A Solution to This Dilemma

There are a few possible solutions:

1. Do nothing and carry on as usual — the it'll be alright on the night solution

2. Soldier on as usual but get more and more people to study CS and undertake other versions of IT training — the bang your head against the wall solution

3. Devise new IT training, along with an IT apprenticeship, which is apposite the current IT demanded in the workplace; make it accessible by means other than expensive 3- or 4-year university courses; make it easily updated as technology changes; and to widen the demography, age-independent, of new IT training entrants. These needs mandate an online course(s).

Hot Topics

The Latest

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

The Case for Radically New IT Training

Terry Critchley

This blog presents the case for a radical new approach to basic information technology (IT) education. This conclusion is based on a study of courses and other forms of IT education which purport to cover IT "fundamentals." It is based on my own decades of IT experience and dogma-free research into current IT literature and media.

Information technology training occurs in numerous forms from computer science (CS) courses, as taught in schools and universities, to other eclectic ones and PC-oriented versions of the computing world. I maintain that these courses, especially CS ones, do not stack up to the needs of the fluid, modern IT as practiced in the workplace, especially the enterprise. My reasoning is as follows:

1. There is, and has been for over two decades, an IT skills shortage which is at its peak today (any day).

2. Practically the only source of CS skills are the schools and universities and, of the CS graduates, over half do not stay in the IT job they were hired for. CS is grossly understaffed with females and a survey I created for the CAS (computing at school) group unearthed major reasons for this female reluctance as: too geekish and theoretical, boring and needs great maths skills. Neither is true of the IT world I inhabited and which I observe and write about today.

3. CS and other curricula, many of which I have studied, do not match even the keywords which typify modern IT as practiced in the workplace. This can be shown by comparing any existing curriculum with the attached keyword list which typifies modern IT. This list has been verified as representative of modern IT by four of my peers in IT.

4. Fully 70% of IT projects fail in degrees from not quite what I wanted to total disaster. This failure rate applies to the more specific area of digital transformation and legacy modernization. In short, nearly every IT activity.

As a result, most businesses are reliant on computers (digital) in a range of ways from their being necessary for us to function to mission critical. This reliance is badly hampered by the drawbacks in skills available, as discussed above.

A Solution to This Dilemma

There are a few possible solutions:

1. Do nothing and carry on as usual — the it'll be alright on the night solution

2. Soldier on as usual but get more and more people to study CS and undertake other versions of IT training — the bang your head against the wall solution

3. Devise new IT training, along with an IT apprenticeship, which is apposite the current IT demanded in the workplace; make it accessible by means other than expensive 3- or 4-year university courses; make it easily updated as technology changes; and to widen the demography, age-independent, of new IT training entrants. These needs mandate an online course(s).

Hot Topics

The Latest

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...