Hands-on learning in the age of AI: Are developer workshops still relevant?

At the 2026 PyCon Australia conference, held in Brisbane, industry veteran Graham Dumpleton delivered a keynote within the DevRel (Developer Relations) track that challenged the prevailing sentiment regarding technical education. As artificial intelligence models continue to dominate the landscape of software engineering, the traditional developer workshop—a cornerstone of community engagement and skill acquisition—faces an existential inquiry. The core of the discourse centered on whether the rise of instantaneous, AI-generated answers has rendered structured, step-by-step practical training obsolete.
The Shift in Developer Education
For over a decade, developer advocacy has been synonymous with the production of tutorials, documentation, and workshops. However, the emergence of advanced Large Language Models (LLMs) has fundamentally altered how developers source information. Data from industry analysts suggests that a significant percentage of routine programming queries, which were previously directed toward mailing lists, Stack Overflow, or GitHub issue trackers, are now resolved via AI assistants in a matter of seconds.
This transition has created a clear dichotomy in the learning process. While AI excels at providing contextualized solutions—adjusting code snippets to a user’s specific operating system or project environment—it operates primarily as a passive knowledge delivery system. The challenge for educators, according to the observations presented at PyCon AU 2026, is that these tools prioritize "correctness" over "learnability." When a tool provides an immediate, accurate answer, it effectively bypasses the cognitive friction required for genuine skill retention.
The Mechanics of "Doing" vs. "Reading"
Educational psychology highlights that deep learning occurs during the struggle to overcome obstacles. In the context of software development, this is often described as the "debugging process." When a learner encounters an error in a live environment, they are forced to deconstruct their own actions, identify the point of failure, and understand the underlying logic of the system.
The current landscape of AI-assisted coding risks eroding this process. In a chat-based interface, a user may receive a correct solution without ever understanding why their initial approach failed. Consequently, the learner lacks the foundational knowledge to address similar issues independently in the future. The PyCon AU presentation underscored three critical advantages of traditional workshops:
- Consequences for Errors: Unlike a chat window, a live workshop environment forces a user to rectify mistakes, which facilitates a deeper understanding of system architecture.
- Productive Friction: The frustration of a broken build or a complex configuration is, ironically, the catalyst for memory consolidation.
- Discovery of Unknowns: AI can answer a specific question, but it cannot prompt a user to explore concepts they do not know exist, such as thread safety or production-level security protocols. A well-designed workshop introduces these hidden complexities in a controlled, linear fashion.
Chronology of the Wrapture Workshop Initiative
The discussion gained practical urgency following the September 2026 release of 24 free, self-serve workshops for the software library "wrapture." These workshops, designed to run directly within a browser via JupyterLab and the Binder platform, serve as a case study for the future of technical education.
The development of these workshops followed a three-phase approach:
- Initial Drafting (Early September 2026): Leveraging AI to outline the basic technical steps and generate boilerplate code.
- Human-Centric Refinement (Mid-September 2026): Manual intervention to adjust "step size," ensuring that the progression of tasks remained challenging but manageable for a novice.
- Community Validation (Late September 2026): The initiative gained significant visibility following endorsements from industry influencers, including developer Simon Willison and the Python Bytes podcast, which acted as a catalyst for adoption.
This timeline reveals a hybrid model: using AI to handle the logistical and formatting overhead, while relying on human expertise to design the pedagogical experience.
Technical Hurdles and Content Strategy
The PyCon AU presentation identified three primary reasons why learners abandon workshops: poor environment configuration, excessive step sizes, and a lack of verification.
Modern tooling has largely solved the "environment" problem. By utilizing containerized, browser-based environments—such as Educates, Killercoda, or Instruqt—instructors can ensure that every participant begins from a synchronized state. This eliminates the "forty minutes of installation" bottleneck that frequently plagued in-person workshops.
However, the "content" problem remains a human domain. The analysis suggests that the most effective workshops employ a "predict-then-verify" rhythm. Instead of instructing a user to run a command, the material asks the user to hypothesize the outcome of a specific configuration change. This pedagogical shift transforms the user from a passive observer of code into an active investigator. Furthermore, the inclusion of verification checks after every potentially volatile step prevents the accumulation of errors, ensuring that the learner reaches the end of the module with a functional understanding of the system.
Broader Industry Implications
The implications for developer advocacy are substantial. As the barrier to generating content decreases due to AI, the value of that content will increasingly depend on its quality, pacing, and ability to foster active participation.
Industry analysts note that while self-serve, curiosity-driven workshops face stiff competition from AI, business-driven training—such as product demonstrations or corporate onboarding—remains robust. The challenge lies in the "discovery problem." With social media and search results increasingly saturated with AI-generated content, the ability of high-quality, human-curated workshops to reach their target audience is hampered.
Moreover, there is a paradoxical relationship between human-led workshops and AI training data. By publishing these structured, high-quality workshops, developers are effectively contributing to the future training sets of the very AI models that challenge their relevance. While this may seem counterintuitive, it ensures that when an AI is eventually asked about a new, niche technology like "wrapture," its response is grounded in the pedagogical framework provided by the original creator.
Conclusion: The Future of Technical Literacy
The overarching consensus from the PyCon AU 2026 session is that the relevance of developer workshops is not a fixed metric but a reflection of the intent behind the interaction. The "do-it-yourself" era of learning is not dead, but it is undergoing a profound evolution.
For technical educators, the mandate is clear: abandon the creation of static, "getting-started" guides, as these are now effectively handled by AI. Instead, focus efforts on creating interactive, high-friction environments that prioritize diagnosis, experimentation, and conceptual depth. As AI becomes the primary interface for information retrieval, the role of the workshop is to serve as a laboratory for the critical thinking that AI cannot replicate.
The future of developer education lies in the middle ground—a synthesis where AI provides the efficiency of instant answers, but the human-led workshop provides the foundational experience required to turn that information into professional competence. Success in this field will be measured not by how much documentation is produced, but by how effectively an instructor can design a curriculum that guides a learner toward a meaningful, hands-on discovery of a subject.







