Anyone can use Copilot.
Developers who use it well are a different tier.
Five modules built around one principle: every line in production is yours, regardless of who wrote it first. Whether you configure Guidewire, build integrations, or work across a broader insurance IT stack — this pathway gives you the systematic habits that make AI-assisted development faster, more rigorous, and worth a rate conversation.
Where AI genuinely accelerates — and what ownership means regardless of authorship.
Systematic review for AI's consistent failure patterns — APIs, boundaries, security.
Log analysis, integration failure diagnosis, root cause vs. symptom discipline.
Documentation, incident communication, and design decision records that compound.
Daily habits, market positioning, and pathway readiness self-assessment.
Three developer profiles. One pathway that works for all of them.
Insurance IT developers work across a spectrum — Guidewire-specific configuration to complex Java integration to broader application development. This pathway serves all three, using Guidewire and insurance-specific examples as the through-line while keeping every pattern applicable to your specific context.
This pathway is built for:
The Guidewire examples throughout are concrete and practical — Gosu code patterns, PolicyCenter API verification, bundle transaction context. If your work is adjacent rather than Guidewire-specific, the review discipline, debugging approach, and communication patterns apply directly to your stack. The ownership principle applies to everyone.
Two kinds of AI-using developers are emerging. Only one commands premium rates.
One uses AI to produce more output faster and lets the volume mask decreased rigour. The other produces more output faster and maintains the same professional ownership standard — catching what AI misses, communicating clearly, building systems that hold up. This pathway is the difference.
Real velocity, not just volume
Boilerplate, scaffolding, unit tests, data transformations, documentation — AI compresses the low-signal work. The time recovered goes to design quality and complex reasoning. You ship more of what matters, faster.
Systematic review, not selective trust
AI has predictable failure patterns in insurance IT development. Invented API methods, boundary condition errors, null handling gaps, security underweighting. Knowing what to look for makes your review faster and more reliable.
A practice worth describing
Developers who win rate conversations don't just say "I use AI tools." They describe a systematic approach — what they review, why, and what the ownership standard means in practice. This pathway gives you that, grounded in insurance IT specifics.
Five modules. Guidewire and insurance IT throughout. Ownership-first from start to finish.
Code at a Different Speed
AI-assisted development isn't about generating code you don't understand — it's about compressing the low-signal parts so your thinking goes to what actually requires a developer. This module maps where the real acceleration lives and establishes the ownership standard that makes it sustainable.
- Where developer time goes — and what AI genuinely changes
- High-value AI use cases for Guidewire and insurance IT development
- Context-rich prompting patterns that produce usable output
- The ownership principle: every line in production is yours
Reviewing What You Didn't Write
AI has consistent, predictable failure patterns — not random errors, but specific categories it gets wrong reliably. Knowing these makes your review faster and more rigorous. This module builds the systematic review discipline that makes AI-assisted development safe to ship.
- AI's consistent failure patterns in Guidewire development — invented API methods, boundary errors, null handling, outdated patterns
- Security considerations AI consistently underweights — logging PII, credentials, authorisation gaps
- The AI code review checklist — systematic coverage, not selective attention
- Using AI to review AI: a legitimate technique with specific limits
Debugging and Root Cause
Debugging is where developer time disappears — reading hundreds of log lines, tracing failures through three integrated systems, distinguishing root cause from symptom. AI compresses the pattern recognition work that makes this so slow.
- Guidewire server log analysis — from wall of text to signal in minutes
- Multi-system integration failure diagnosis — PolicyCenter, ClaimCenter, billing, external APIs
- Root cause vs. symptom — the distinction that prevents recurrence in insurance systems
- The iterative debugging conversation — and when to reset a wrong hypothesis
Technical Communication
Technical communication that compounds professionally — documentation that serves future developers, incident communications that maintain trust under pressure, design decision records that pay returns for years. AI removes the blank page friction; you supply the judgment and accuracy.
- Audience matrix — what developers, QA, BAs, PMs, and sponsors actually need
- Technical documentation: AI handles the "what," you add the "why"
- Incident communication accuracy — the verification discipline that prevents bigger problems
- Design decision records with complete consequences, not just benefits
Your AI-Augmented Developer Practice
Bring the full pathway together. What an AI-augmented developer day actually looks like in insurance IT, how to describe this capability in a premium engagement conversation, and a personal readiness assessment across all five modules.
- Concrete daily habits — scaffolding, review, debugging, documentation, incidents
- How to describe your practice when a client asks about AI code quality
- Generic vs. premium positioning — what makes the difference in a rate conversation
- Personal readiness self-assessment across all five pathway competencies
What this pathway says about you on your Icon Profile.
Systematic AI-augmented development
You don't just use AI tools — you apply a specific review discipline for the failure patterns they produce in insurance IT development. Context-rich prompting, API method verification, boundary condition tracing, security review. Faster output with the same professional ownership standard.
Guidewire and insurance IT context
The pathway is built around Guidewire PolicyCenter and ClaimCenter development patterns, Gosu and Java integration contexts, and the specific regulatory and data handling environment of Canadian insurance IT. That specificity is visible in your Icon Profile signals.
Ownership-first engineering practice
Every line in production is yours. You can explain any section of code you submit — regardless of whether AI wrote the first draft. You produce clear technical documentation, accurate incident communications, and design decision records that serve the teams who come after you.
Explore adjacent Academy pathways.
Start with Module 01 — no account required.
All five modules are open access. Start now, track your progress through the pathway, and unlock your Icon Profile signals when you complete Module 05.