Archive

Training

The Uncomfortable Truth: Why Developer Training Is a Waste of Time

There’s an entire industry built around “improving” software developers. Conferences, workshops, bootcamps, online courses, books, certifications—billions of dollars spent annually on the promise that if we just train developers better, we’ll get better software. It’s time to say what many of us have privately suspected: it’s all just theater.

Here’s why investing in developer training is increasingly pointless, and why organisations would be better served directing those resources elsewhere:

  1. Nobody’s actually interested in improvement
  2. Developers don’t control what actually matters
  3. GenAI has fundamentally changed the equation

Let’s examine each of these uncomfortable truths.

1. Nobody’s Actually Interested in Improvement

Walk into any development team and ask who wants to improve their craft. Hands will shoot up enthusiastically. Now watch what happens over the next six months. The conference budget goes unused. The book club fizzles after two meetings. The internal tech talks attract the same three people every time. The expensive training portal shows a login rate of less than 15%. Personal note: I have seen this myself time and again in client organisations.

The uncomfortable reality is that most developers have found their comfort zone and have little to no genuine interest in moving beyond it. They’ve learned enough to be productive in their current role, and that’s sufficient. The annual performance review might require them to list “professional development goals” but these are box-checking exercises, not genuine aspirations. When developers do seek training, it’s often credential-seeking behavior—resume-building for the next job search, a.k.a. mortgage-driven development, not actual skill development for their current role.

This isn’t unique to software development. In most professions, once practitioners reach competence, the motivation for continued improvement evaporates. The difference is that in software, we’ve created an elaborate fiction that continuous learning is happening when it definitely isn’t. The developers who genuinely seek improvement are self-motivated outliers who would pursue it regardless of organisational investment. They don’t need your training programs; they’re already reading papers, experimenting with new technologies, and pushing boundaries on their own time.

2. Developers Have No Control Over What Actually Matters

Even if a developer emerges from training enlightened about better practices, they return to an environment that makes applying those practices simply impossible. They’ve learned about continuous deployment, but the organisation requires a three-week approval process for production releases. They’ve studied domain-driven design, but the database schema was locked in five years ago by an architecture committee. They’ve embraced test-driven development, but deadlines leave no time for writing tests, and technical debt is an accepted way of life.

The factors that most impact software quality—architecture decisions, technology choices, team structure, deadline pressures, hiring practices, organisational culture, the social dyname—are entirely outside individual developers’ control. These are set by management, architecture boards, or historical accident. Having developers trained in excellent practices but embedded in a dysfunctional system is like teaching someone Olympic swimming techniques and then asking them to compete while chained to a cinder block. (See also: Deming’s Red Bead experiment).

Moreover, the incentive structures in organisations reward maximising bosses’ well being, not e.g. writing maintainable code. Developers quickly learn that the skills that matter for career advancement are political navigation, project visibility, stakeholder management and sucking up—not technical excellence. Training developers in better coding practices while maintaining perverse incentives is simply theater that lets organisations feel good about the charade of “investing in people” while changing absolutely nothing that matters.

3. GenAI Has Fundamentally Changed the Equation

The emergence of generative AI has rendered much of traditional developer training obsolete before it’s even delivered. When Claude or GPT can generate boilerplate code, explain complex algorithms, refactor legacy systems, and even architect solutions, what exactly are we training developers to do? (Maybe AI has a more productive role to play in helping developers maximise their bosses’ well being).

The skills we’ve traditionally taught—memorising syntax, understanding framework details, knowing design patterns, debugging techniques—are precisely the skills that AI handles increasingly well. We’re training developers for skills that are being automated even as we conduct the training. The half-life of technical knowledge has always been short in software, but AI has accelerated this to the point of absurdity. By the time a developer completes a course on a particular framework or methodology, AI tools have already internalized that knowledge and can apply it faster and more consistently than any human (usual AI caveats apply).

The argument that developers need to “understand the fundamentals” to effectively use AI is wishful thinking from an industry trying to justify its existence. Junior developers are already shipping production code by describing requirements to AI and validating outputs. The bottleneck isn’t their understanding—it’s organisational factors like the social dynamic, relationships, requirements clarity and system architecture. Training developers in minutiae that AI handles better is like training mathematicians to use slide rules in the calculator age.

The Hard Truth

The developer training industry persists not because it works, but because it serves organisational needs that have nothing to do with actual improvement. It provides HR with checkboxes for professional development requirements. It gives managers a feel-good initiative to tout in interviews and quarterly reviews. It offers developers a sanctioned way to take a break from the grind. Everyone benefits except the balance sheet.

If organisations genuinely wanted better software, they’d stop pouring money into training programs and start fixing the systems that prevent good work: rigid processes, unrealistic deadlines, toxic relationships, flawed shared assumptions and beliefs, and misaligned incentives. They’d hire fewer developers at higher salaries, giving them the time and autonomy to do quality work. They’d measure success by folks’ needs met rather than velocity and feature count. But that would require admitting that the problem isn’t the developers—it’s everything else. And that’s a far more uncomfortable conversation than simply booking another training workshop.

Fuggedabaht Training: The Future of Learning in Tech

In the realm of tech education and learning, few statements are as provocative and thought-provoking as Oscar Wilde’s assertion:

“Education is an admirable thing, but it is well to remember from time to time that nothing that is worth knowing can be taught.”

This paradoxical wisdom serves as the perfect launching point for an exploration of learning in the tech industry. In a world where formal training has long been the go-to method for skill development, Wilde’s words challenge us to reconsider our approach fundamentally.

In the dizzying world of technology, where today’s innovation is tomorrow’s legacy system, how do we truly learn? The tech industry has long relied on training as its educational backbone, but is this approach ever fit for purpose? Let’s embark on a journey to unravel this question and explore the future of learning in tech.

The Training Trap: Why It’s Not Enough

Picture this: You’ve just completed an intensive week-long course on the latest programming language. You’re buzzing with newfound knowledge, ready to conquer the coding world. Fast forward three weeks, and you’re staring at your screen, struggling to remember the basics. Sound familiar?

This scenario illustrates what Richard Feynman, the renowned physicist, meant when he said:

“I learned very early the difference between knowing the name of something and knowing something.”

Training often gives us the illusion of learning. We walk away with certificates and buzzwords, but when it comes to actually applying this knowledge, we find ourselves fumbling in the dark.

The Forgetting Curve: Our Brain’s Sneaky Saboteur

Enter Hermann Ebbinghaus and his infamous “forgetting curve”. This isn’t just some dusty psychological theory; it’s a real phenomenon that haunts every training session and workshop.

As the curve shows, without active recall and application, we forget about 70% of what we’ve learned within a day, and up to 75% within a week. In the context of tech training, this means that expensive, time-consuming courses might be yielding diminishing returns faster than you can say “artificial intelligence”.

Real World vs. Training Room: A Tale of Two Realities

Training environments are like swimming pools with no deep end. They’re safe, controlled, and utterly unlike the ocean of real-world tech problems. This disparity leaves many students floundering when they face their first real challenge.

Moreover, in an industry where change is the only constant, static training curricula are often outdated before they’re even implemented. As Alvin Toffler presciently noted:

“The illiterate of the 21st century will not be those who cannot read and write, but those who cannot learn, unlearn, and relearn.”

The Bootcamp Boom: A Silver Bullet or Fool’s Gold?

In recent years, coding bootcamps have exploded onto the tech education scene, promising to transform novices into job-ready developers in a matter of weeks or months. But do they truly bridge the gap between traditional training and real-world demands?

The Promise of Bootcamps

Bootcamps offer an intensive, immersive learning experience that focuses on practical skills. They aim to provide:

  1. Rapid skill acquisition
  2. Project-based learning
  3. Industry-aligned curriculum
  4. Career support and networking opportunities

For many career changers and aspiring developers, bootcamps represent a tantalizing shortcut into the tech industry.

The Reality Check

While bootcamps have undoubtedly helped many individuals launch tech careers, they’re not without their criticisms:

  1. Skill Depth: The accelerated pace often means sacrificing depth for breadth. As one bootcamp graduate put it:

    “I learned to code, but I didn’t learn to think like a developer.” [and what does it even mean to “think like a developer, anyway?]

  2. Market Saturation: The proliferation of bootcamps has led to a flood of entry-level developers, making the job market increasingly competitive.
  3. Varying Quality: Not all bootcamps are created equal. The lack of standardisation means quality can vary wildly between programs.
  4. The Long-Term Question: While bootcamps may help you land your first job, their long-term impact on career progression is still unclear.

Bootcamps: A Part of the Solution, Not the Whole Answer

Bootcamps represent an interesting hybrid between traditional training and more innovative learning approaches. At their best, they incorporate elements of experiential learning and peer collaboration. However, they still operate within a structured, time-bound format that may not suit everyone’s approach to learning or career goals.

As tech leader David Yang notes:

“Bootcamps can kickstart your journey, but true mastery in tech requires a lifetime of learning.”

In the end, we might choose to view bootcamps as one possible tool in a larger learning toolkit, rather than a one-size-fits-all solution to tech education.

Reimagining Learning: The Tech Education Revolution

So, if traditional training isn’t the answer, what is? Let’s explore some alternatives that are already showing promise:

  1. Experiential Learning: Remember building your first website or debugging your first major error? That’s experiential learning in action. As Confucius wisely said, “I hear and I forget. I see and I remember. I do and I understand.”
  2. Continuous Learning Culture: Imagine a workplace where learning is as natural as breathing. Google’s no defunct “20% time” policy, which allowed employees to spend one day a week on side projects, was a prime example of this philosophy in action.
  3. Peer-to-Peer Knowledge Sharing: Some of the best learning happens organically, through conversations with colleagues. Platforms like Stack Overflow have harnessed this power on a global scale.
  4. Curiosity-Driven Exploration: What if we treated curiosity as a key performance indicator? Companies like 3M, which encourages employees to spend 15% of their time on self-directed projects, are leading the way.

Caution: Whilst experiential learning has its merits, it fails abjectly to counter groupthink, learning of the wrong things, and relatively ineffective shared assumptions and beliefs. Other approaches e.g. Organisational Psychotherapy can address the latter.

The Path Forward: Embracing the Learning Revolution

As we stand at the crossroads of traditional training and innovative learning approaches, it’s clear that a paradigm shift is not just beneficial—it’s essential. The future of learning in tech isn’t about more training; it’s about creating environments that foster continuous, experiential, and collaborative learning, whilst simultaneouly growing the ability to think critically, think of wider systems (systems thinking) and constantly surface and reflect together on shared assumptions and beliefs.

So, the next time you’re planning a training session, pause and ask yourself: Is this the best way to foster real learning? What about more engaging, effective approaches we could take?

In the words of William Butler Yeats, “Education is not the filling of a pail, but the lighting of a fire.” Isn’t it time we stopped trying to fill pails and started lighting fires in the tech industry.

What are your thoughts? How well has training served your needs, and how has your learning journey in tech evolved beyond traditional training? Please share your experiences in the comments below!

Training’s Empty Promises

What’s Wrong with Training?

Let’s cut to the chase: Training doesn’t work when it comes to changing behaviours. While organisations pump vast amounts of money into training programmes, hoping for transformative effects, the outcomes never match the investment. You’re probably wondering why. It’s high time we scrutinise what’s really going on.

What About the Hawthorne Experiment?

In the late 1920s, the Hawthorne Experiment was conducted at the Western Electric Hawthorne Works in Chicago. Researchers changed various environmental conditions for workers to see if productivity improved. To everyone’s surprise, almost any change led to increased productivity. It wasn’t the training or the changed conditions that boosted productivity; it was the fact that someone was paying attention to the workers – and their needs. It showed that behavioural change doesn’t stem from training sessions but from the environment and context in which people operate.

How Do Methods Differ?

Training often employs a fixed method, aiming to produce quantifiable improvements in performance. This approach assumes that humans are like machines: input a certain variable (in this case, training) and expect an improved output (better behaviour or skills). But unlike machines, humans have feelings, motivations, and personal circumstances that training methods can’t address. Where’s the psychology? Absent?

Is There an Alternative?

Certainly, and it’s not another fancy training programme. Changing behaviours often requires a more holistic, systemic approach rooted in psychology, systems thinking and group dynamics. That means looking at organisational culture, team dynamics, leadership styles and the paramount impact of “the system” (the way the work works). Engage with the issues that truly matter to people – their needs – and you’re more likely to see lasting change. Simply put, training in isolation is a lost cause.

What’s the Bottom Line?

Training won’t change behaviours. Whether it’s a disregard for approaches that consider the human element, or the illusion of improvement illustrated by experiments like Hawthorne, it’s clear that training isn’t the magical cure-all many believe it to be. The sooner organisations realise this, the sooner they can take steps towards meaningful change.

Coaching the Coaches?

Who’s Coaching New Coaches?

When an organisation decides to bring coaching into its culture, the focus is usually on its employees. Yet the coaches themselves are often left to endure rigid training, which stands at odds with the coaching philosophy. If organisations genuinely believe in coaching, why don’t they extend this to their new coaches?

What’s Wrong with Training Compared to Coaching?

Training enforces a rigid structure, pushing predetermined information towards the participant. This approach is inflexible and impersonal, falling short of individual needs. In contrast, coaching is a dynamic, two-way relationship tailored to the individual’s unique needs and objectives.

Why Do Organisations Stick to Training New Coaches?

Many organisations default to traditional training methods, even for roles better suited for coaching. This inclination towards training could be seen as a glaring oversight and a lack of genuine commitment to the coaching approach.

Is Training New Coaches a Misstep?

Absolutely. Training, with its push approach, is fundamentally ill-equipped for roles that demand behavioural change and personal development. Especially in the realm of Collaborative Knowledge Work. By clinging to training for their new coaches, organisations contradict and undermine their supposed endorsement of coaching.

Why Is Coaching New Coaches the Superior Option?

Coaching, unlike training, draws out an individual’s inherent potential. It enhances both the effectiveness and empathy of new coaches and helps foster a real coaching culture within the organisation.

What’s the Next Step?

Organisations might choose to move beyond training and embrace a coaching-centric approach universally, starting with their newest coaches. Doing so is not just lip service to a trend; it’s a necessary evolution for genuine development.

Is Coaching Itself Beyond Reproach?

As we sing the praises of coaching over training, it’s crucial to consider a larger issue: Is coaching itself the end-all solution for organisational development? No. According to quality management expert W. Edwards Deming’s 95/5 rule, most problems (95%) are the fault of the system, not the individual. Coaching often targets individual behaviours—the “5%”—and overlooks systemic issues that could be the root cause of performance limitations. Organisations might choose to scrutinise their coaching programmes to ensure they’re not just treating symptoms while ignoring the disease.

Conclusion: Where Does This Leave Us?

If organisations are serious about adopting coaching, they might choose to apply the coaching approach at all levels, including new coaches. However, it’s worth reflecting on whether coaching itself, focused as it often is on the “5%”, is enough to address the underlying systemic issues that are impeding progress. To achieve lasting change and growth, organisations must consider systemic improvements as paramount. Anything less represents a missed opportunity.

Training For All The Wrong Skills

Are We Training People For the Wrong Skills?

In business and software development, we’ve got a misalignment. We’re so wrapped up in perfecting the technical, we lose sight of the human. Developers are trained to churn out code more quickly, code that’s faster, cheaper, and more reliable, but are they learning how to solve real-world problems? Testers are trained to find bugs, but not how to prevent them. The result: technically proficient software that either nobody wants or that arrives late and over budget, or both.

Technical Matters?

Yes, quality code is essential. Yet, it’s by no means the end-all and be-all. A developer isn’t just a code-writing machine; they’re attendants. The fixation on coding and computing skills above all else turns them into technicians rather than holistic thinkers capable of understanding and meeting folks’ needs. When developers are pigeonholed into this role, organisations miss out on the broader impact their expensive developers could be making.

What About Bugs?

Finding bugs is a red herring – what if we could prevent them in the first place? Testers are often pigeonholed into merely identifying issues rather than participating in a more proactive approach. This approach costs time, money, and may even reduce the software’s overall quality because the focus is on fixing, not preventing. The need for speed in bug-finding diverts attention from other valuable forms of contribution, like feature development and needs validation (making sure the product meets the real needs of all the Folks That Matter™.

What’s the Cost?

When we narrow our focus to speed, efficiency, and defect detection, we end up inflating costs and extending delivery times. Software development isn’t just about churning out lines of code or ticking off a testing checklist. It’s a more nuanced art that blends technical skills with an understanding of the needs of all the Folks That Matter™.

Where’s the User in All This?

In the chase for technical mastery, it’s easy to forget the end-user. Products, at their core, are intended to make lives easier, to attend to folks needs. When developers and testers are not trained to master these things, we end up with products that are high on features but low on utility.

So What’s the Solution?

If we’re to correct this misalignment, we need a cultural shift. We might choose to reorient our training and development programmes. For developers, this means less emphasis on speed and more on understanding who matters, and then discovering and meeting these folks’ needs. For testers, a shift from just finding bugs to a more holistic approach to quality via defect prevention (Cf. ZeeDee) would be transformative.

Where Do We Go from Here?

The technical aspects of software and product development are, without a doubt, essential. But they aren’t the whole story. By shifting our focus to include all the needs of all the Folks That Matter™, we can create products that not only work but makes a difference. The first step? Acknowledging that we’ve been training for all the wrong skills.

The Folly of Training for Behaviour Change

The Illusion of Training-Induced Change

Let’s start with a provocative statement: Training doesn’t change people; it only gives them options. There’s a widespread belief that sending staff on training courses is the magic key to fixing various performance or behavioural issues. But if you’re aiming to change people’s behaviours through training, you’re on to a loser before you even start.

The Gulf Between Teaching and Learning

Teaching and learning, though often used interchangeably, are not synonymous. Teaching implies the transfer of knowledge or skills from one person to another. Learning, however, is a more intricate process, deeply personal and emotionally charged. It involves not just the intake of information but the reshaping of perspectives, attitudes, and ultimately, behaviours.

People can be taught without learning a single thing. They’ll nod, take notes, even pass tests, but once they’re back in their familiar environments, it’s business as usual. Why? Because learning has only happened when behaviours have changed.

The Dynamics of Behaviour Change

Behaviour isn’t a switch you can flick on or off through an afternoon workshop. It’s a complex mosaic of habit, culture, context, motivation, and personal choice. Each person’s behaviour is influenced by a labyrinth of internal and external factors, which can’t be manoeuvred through PowerPoint slides and handouts.

The secret sauce in behaviour change is not teaching or training. It’s learning. And how does learning happen? Through curiosity—a deeply intrinsic motivator that spurs us to explore, challenge norms, and grow.

Radical Curiosity: The Gateway to Learning

If you’ve been chasing the mirage of training-induced change, redirect your energies towards fostering an environment that celebrates ‘Radical Curiosity‘. This is a step beyond the garden-variety curiosity that makes us click on an interesting headline. Radical Curiosity is the relentless pursuit of ‘why’ and ‘how’, the unquenchable thirst for knowledge that disrupts conventional wisdom.

When you are radically curious, you don’t just want to know what works; you want to understand why it works and how you can make it better. This is the sort of curiosity that can drive genuine learning and transformative behaviour change.

How to Cultivate Radical Curiosity

Here’s the million-dollar question: how do you instil Radical Curiosity in a team or an organisation? Here are some thoughts:

  1. Open Dialogue: Encourage questions and discussions that challenge the status quo.
  2. Safe Spaces: Create an environment where people feel secure enough to share radical thoughts without fear of ridicule or judgment.
  3. Encourage Exploration: Give people the freedom to explore new ideas, methods, and even make mistakes.
  4. Reflective Practice: Facilitate sessions where team members can reflect on what they’ve learned and how they can apply it to change their behaviours.

The Bottom Line

If you’re investing in training to change behaviour, you’re on shaky ground. The change you seek is rooted in the fertile soil of learning, nourished by the waters of Radical Curiosity. Replace your training programmes with initiatives that nurture curiosity, and watch how behaviours transform organically. That’s when you know learning has truly happened.

The Joy of Unscripted Learning

In the grand dance of life, each of us has our own rhythm, our own unique cadence. Yet, when it comes to learning, we’re often coerced into moving in lockstep, following the tempo set by impersonal online tutorials. Isn’t it time we break free from this uniform waltz and explore the thrilling unpredictability of our own intellectual choreography?

The Romance of Discovery

In the world of learning, online tutorials often serve as a pragmatic guide to those who prefer a step-by-step navigation. But my heart sings to a different tune. I’m an advocate for the romanticism of exploration, of stumbling upon a discovery without a prescribed set of instructions.

Imagine, if you will, a world where every creative endeavour is led by a predetermined path. It’s rather like reducing a breathtaking, improvised dance performance to a paint-by-numbers exercise. Yes, online tutorials are efficient, but don’t they sap the very marrow of our learning experience, the thrill of the unpredictable, the joy of the unforeseen breakthrough?

A Ballet of the Mind

Then let’s think about pace. Tutorials tend to act like a one-size-fits-all suit, but isn’t learning a more personal affair? A ballet of the mind, it unfolds at its own rhythm, dancing to the beat of each unique learner. In my book, tutorials might as well be straitjackets, stifling the learner’s own interpretive twists and turns.

Personal Discovery

So, here’s a revolutionary notion – learning, like life, isn’t meant to be a straightforward march. It’s a meandering journey. Each stumble, each hard-earned triumph, shapes us, makes us who we are. To surrender that process for the easy route of tutorials is to trade the richness of personal discovery for the mundanity of consensus and received “wisdom”. Let’s embrace our own intellectual adventures and step away from the conveyor belt of homogenised knowledge.

A Learning Path for The Team Fruit Bowl

Buiilding a Better Team

My most recent book “The Team Fruit Bowl” aims to provide a host of practical insights, and a road map for making your team better.

To help The Team Fruit Bowl‘s readers along that road, here’s a learning path for the book.

Learning Path

  1. Introduction to the Concept: Begin by understanding the fundamental premise of the book – the idea of comparing different team dynamics to various fruits. Familiarize yourself with the overall structure of the book and the key themes it explores.
  2. Deep Dive into Individual Chapters: Each chapter of the book focuses on a different fruit and the team dynamics it represents. Read each chapter carefully, taking notes on the key takeaways and practical applications. Remember, you don’t have to choose one fruit as a model for your team. Instead, consider the unique aspects of each fruit and how they might apply to your team’s context:
    • Team Apple
    • Team Banana
    • Team Orange
    • Team Grape
    • Team Pineapple
    • Team Watermelon
    • Team Strawberry
    • Team Blueberry
    • Team Peach
    • Team Lemon
    • Team Raspberry
    • Team Coconut
    • Team Kiwi
    • Team Mango
    • Team Kumquat
    • Team Pear
  3. Reflection and Discussion: After each chapter, reflect on the lessons learned. How do they apply to your team? What elements resonate with your team’s current dynamics? If you’re reading this book as a team, this would be a good time to have a group discussion.
  4. Practical Application: Start applying the lessons learned to your team. This could be in the form of new team-building activities, changes in communication, or adjustments to your team’s structure or culture. Remember, change takes time, so be patient and persistent. And most importantly, feel free to mix and match the elements that best suit your team’s context.
  5. Continuous Learning: Once you’ve gone through all the chapters, don’t stop there. Revisit the book regularly, reflect on the changes you’ve made, and continue to learn and adapt. The journey to a high-performing team is ongoing, and there’s always more to learn.
  6. Evaluation: After a few months of applying the lessons from the book, take some time to evaluate. What changes have been effective? What still needs work? Use this evaluation to guide your ongoing learning and development as a team.

Remember, the goal of this learning path is not just to read the book, but to truly understand and apply its insights to improve your team’s dynamics and performance. The beauty of “The Team Fruit Bowl” is that it allows you to pick and choose the elements that best suit your team, creating a unique blend that’s just right for your context.

Teaching Others: The Ultimate Learning Hack

The best way by far to learn is to teach others. This statement has been echoed by many educational experts and researchers over the years, yet it is still not implemented in many teaching and training situations. It is a well-known fact that teaching is a powerful tool for learning, but why is it not used more often?

One of the reasons for this is that traditional teaching methods have been based on a one-way flow of information. The teacher imparts knowledge to the student, who is expected to absorb it and regurgitate it in exams. This approach may work for some subjects, but it is not effective for all.

To truly understand a subject, one needs to engage with it in a more active and interactive way. By teaching others, we are invited to break down complex concepts into simpler parts, and explain them in a way that others can understand. This not only helps to reinforce one’s own understanding of the topic but also helps to identify areas where one may have gaps in one’s knowledge.

Another benefit of teaching others is that it helps to develop critical thinking and problem-solving skills. When teaching others, one needs to be able to anticipate the questions that may arise, and be able to come up with solutions on the spot. This helps to develop a more holistic understanding of the subject, and also helps to develop transferable skills.

So why are so few teaching and training situations based on this principle? One reason is that it can be challenging to implement in practice. It requires a shift in mindset from the traditional teacher-led approach to a more collaborative approach where the emphasis is on active learning and student engagement.

Another reason is that there may be resistance from students and teachers who are used to the traditional approach. It can be daunting to take on the role of a teacher, and some students may feel uncomfortable with the idea of peer-to-peer teaching (it’s hard work!).

Despite these challenges, there are many examples of successful teaching and training situations that are based on the principle of peer-to-peer teaching. From peer tutoring in schools to mentorship programmes in the workplace, these approaches have been shown to be effective in promoting learning and development.

In conclusion, the best way by far to learn is to teach others. By engaging in active learning and peer-to-peer teaching, we can develop a deeper understanding of a subject, and also develop transferable skills that can be applied in a range of different contexts. While there may be challenges to implementing this approach, the benefits are clear, and we might choose to look for ways to integrate it into our teaching and training programmes.

 

Who’s got your back when it comes to remaining relevant in a fast-changing skills market? Who can you rely on to point out new skills that will become vogue in one, five, ten years’ time?

Given the time it takes to develop such skills to the point where they become useful to clients and employers, when do you start ramping up new skills in anticipation of emergent demand for them?

Especially when some new skills area suggests a sea-change from your existing skill set and comfort zone?

Or maybe you’re just accepting of increasing irrelevancy and declining rates of pay?

Highlight Problems, Avoid Solutions

It’s wayyy easier to provide solutions than to help folks find their own solutions. What are the consequences of this observation?

  • For consultants, trainers, pseudo-coaches and others whose income depends on selling “solutions”?
  • For folks seeking long-term, permanent solutions to their problems?
  • For folks who choose to hire consultants or other experts to solve their problems for them?
  • For folks habituated to delegating the finding of solutions to their problems to others?

Voltaire asks us a rhetorical question:

“Is there anyone so wise as to learn by the experience of others?”

~ Voltaire

I’ll not be offering any solutions to this conundrum. I am available help you along the path of finding your own.Do get in touch!

#IANAC (I am not a consultant).

– Bob

Further Reading

Rother, M. (2010). Toyota Kata: Managing People For Continuous Improvement And Superior Results. Mcgraw-Hill.
Marshall, R.W. (2021). Memeology: Surfacing And Reflecting On The Organisation’s Collective Assumptions And Beliefs. [online] leanpub.com. Falling Blossoms (LeanPub). Available at: https://leanpub.com/memeology/ [Accessed 16 Jun 2022].

It’s not that developer training is expensive (although it is), it’s whether it’s good value (high ROI, improves software delivery). It’s neither.

Would you like to talk it through?

Are “software developer competency” and “software product delivery” complementary, compatible, or oppositional?

“There are no bullet points in The Sermon on the Mount.”

Education is all wrong: Training doesn’t work. Teaching doesn’t exist. See: http://t.co/5GQ8RSjp