For Developers Who Want to Build Software That Matters in the Age of AI
Nothing Changes About Good Software Engineering
AI is changing how software is designed, built, and verified but not what makes it good. The AI Capabilities Transformation for Developers helps you strengthen the human capacities that matter most: seeing systems clearly, thinking critically, designing for change, guiding AI effectively, and continuously improving your craft.
Welcome to the AI Capabilities Transformation (ACT)
Over the next few minutes you’ll discover five capabilities that are becoming more valuable—not less—as AI transforms software development.
- See systems before changing them.
- Think with AI instead of simply asking it for answers.
- Design software that remains easy to change.
- Build through thoughtful collaboration rather than delegation.
- Reflect so every project makes you a better developer.
What capabilities will support you in the age of AI?
The World Has Changed
Software development has always evolved.
We’ve moved from assembly language to high-level languages, from procedural programming to objects, from waterfall to Agile, from monoliths to the cloud. Every generation has asked developers to learn, adapt, and grow.
AI is the latest chapter in that story. But this time, something different is happening.
For the first time, a machine can generate code. That doesn’t make experience less valuable. It reveals what experience really is.
The developers who thrive won’t simply know more frameworks or write more code. They’ll see systems more clearly, make better decisions, design for change, guide AI thoughtfully, and continue learning throughout their careers.
Those aren’t new abilities. They’re the ones great developers have always been building.
The Challenge
Software developers have always embraced change. This feels different. Not because change is new. Because the pace is unlike anything we’ve experienced before.
The tools improve every week. New models appear every month. Advice changes almost daily. It’s difficult to know what deserves your attention and what will disappear tomorrow.
Some days AI feels like a trusted collaborator. Other days it feels unpredictable. Sometimes it accelerates your work. Sometimes it creates more work than it saves.
You’re expected to move faster while maintaining quality. To experiment without sacrificing judgment. To learn continuously while still delivering software that people depend on. If you’ve found yourself wondering what skills will matter most over the next decade…
You’re not alone.
The Real Opportunity Nobody Sees
Like you, I’ve spent years refining my craft—learning new languages, frameworks, tools, and ways of working. Some of those technologies have faded away. Others have become so commonplace that we hardly think about them anymore. That’s the nature of software development. We build our careers on learning, adapting, and growing.
What has surprised me isn’t how much AI can do. It’s what AI has helped me see.
The knowledge I’ve accumulated over thirty years isn’t becoming less valuable. It’s becoming easier to apply because AI can help with the mechanics. What has become more valuable is the part that was always hardest to teach: judgment. Discernment. Understanding the problem before reaching for a solution. Seeing the forces at work in a design. Knowing what to preserve and what to change. Caring about the people who will inherit the software long after we’ve moved on.
AI didn’t diminish what made me a software developer. It revealed what had always mattered most.
I don’t think this is just a technological transition. I think it’s a professional one, and perhaps even a personal one. It’s inviting us to rediscover what our craft has always been about. Not writing more code, but bringing clarity where there is confusion, creating software that serves people well, and helping others navigate change with confidence and care.
A Framework for Becoming the Developer the Future Needs
As I’ve worked with AI over the past few years, one realization kept returning. The biggest breakthroughs rarely came from discovering a better prompt. They came from seeing problems more clearly, asking better questions, designing more thoughtfully, collaborating intentionally, and reflecting on what I was learning. Eventually I realized these weren’t isolated skills. They were connected. Together, they form the foundation of how I think about developing software in the age of AI.
SEE
Understand before changing.
Develop the habit of observing systems before acting. Learn to identify forces, recognize patterns, understand the domain, and describe what you see before reaching for a solution.
Micro-habits
- Describe before changing.
- Identify forces and relationships.
- Model the domain.
- Separate observation from interpretation.
THINK
Reason before responding.
Use AI as a thinking partner rather than an answer generator. Clarify intent, challenge assumptions, explore alternatives, and make deliberate decisions.
Micro-habits
- Clarify intent.
- Ask “Why?”
- Test assumptions.
- Explore alternatives.
DESIGN
Build for change.
Create software that remains simple, extensible, and verifiable even as requirements evolve.
Micro-habits
- Keep designs simple.
- Design for adaptability.
- Verify continuously.
- Refactor with purpose.
BUILD
Guide the collaboration.
Work with AI intentionally rather than delegating blindly. Provide context, establish constraints, review critically, and build incrementally.
Micro-habits
- Demonstrate your style.
- Guide rather than delegate.
- Ground AI with context.
- Verify before accepting.
REFLECT
Learn continuously.
Turn every project into an opportunity to deepen your understanding, refine your practice, and strengthen your judgment.
Micro-habits
- Retrospect regularly.
- Capture insights.
- Unlearn outdated habits.
- Share what you’ve learned.
None of these capabilities are entirely new. If you’ve been developing software for years, you’ve probably been strengthening them all along—often without giving them names. What AI does is make them visible. It exposes the difference between generating code and creating software that truly serves people. My hope is that this framework gives you a language for capabilities you may already possess, and a path for developing them more intentionally.
Throughout the experience you’ll…
✓ Collaborate with other developers
✓ Experiment with AI on real problems
✓ Practice new thinking habits
✓ Reflect on your own work
✓ Learn from experienced practitioners
✓ Leave with techniques you can use immediately
Real Learning Changes How You See
One of the things I’ve learned after teaching thousands of professional software developers is that people rarely change because someone explains an idea well.
They change because they experience something that changes how they see.
That’s why ACT isn’t built around lectures or long presentations. Yes, I’ll introduce new ideas, but we’ll spend most of our time exploring them together. You’ll work through real scenarios, collaborate with other developers, reflect on your own experience, and experiment with AI in ways that reveal patterns you may never have noticed before.
Some of the most valuable moments don’t happen while I’m speaking. They happen during a discussion with another participant, while watching someone approach a problem differently, or when a simple exercise suddenly makes something click.
Those moments are difficult to manufacture in a traditional classroom, but they’re exactly what this experience is designed to create.
Because interaction changes the learner.
Software development has always been a collaborative profession. We learn by building, by questioning one another, by testing ideas, by reflecting on what worked and what didn’t.
I believe learning to work with AI should feel the same way.
You’ll leave with practical techniques you can apply immediately, but my hope is that you’ll leave with something even more valuable: a different way of thinking about software development, about collaboration, and about your own role in shaping the future of our profession.
You’ll continue to think about this long after the experience and you’ll draw on the skills for years.
We’ll spend less time trying to memorize techniques and more time developing the habits of mind that will serve you for the rest of your career.
What You’ll Take Back With You
When you return to work after ACT, you won’t just have new ideas. You’ll have new ways of working.
You’ll leave with practical habits you can begin using immediately, including:
- Better ways to collaborate with ChatGPT, Claude, Copilot, and other AI tools.
- A framework for deciding when to trust AI—and when not to.
- Techniques for keeping AI grounded in your team’s architecture, coding standards, and design principles.
- Better prompts—but more importantly, better conversations.
- Practical ways to review AI-generated code instead of simply accepting it.
- New approaches to design, refactoring, testing, and code reviews.
- Exercises you can continue practicing with your own team.
- A vocabulary for discussing AI collaboration that everyone on your team can share.
Most participants tell me they begin applying ideas from ACT the very next day.
The deeper transformation unfolds over the months that follow.
The Transformation
For as long as I’ve been teaching software development, I’ve believed that the greatest transformations don’t happen because someone learns a new technique. They happen because someone begins to see themselves differently.
I’ve watched developers discover confidence they didn’t know they had. I’ve watched quiet people become thoughtful leaders because they learned to ask better questions. I’ve watched experienced engineers rediscover the joy of learning after years of feeling like they were simply keeping up.
That’s the opportunity I hope ACT creates for you. Not because I have answers you don’t. Because I believe you already possess far more than you may realize. My role isn’t to change who you are. It’s to create the conditions where you can recognize and intentionally develop the capabilities that have been growing throughout your career.
When that happens, something shifts. You stop looking to AI for certainty and begin using it to deepen your own understanding. You stop worrying about whether you’ll keep up with the next tool and begin trusting your ability to learn whatever comes next. You become the person who brings clarity when problems are unclear, when decisions are difficult, and when thoughtful leadership matters most.
Not because you know everything. Because you’ve learned how to see. How to think. How to design. How to collaborate. How to keep growing. Those are capabilities that will serve you long after today’s models and today’s tools have been replaced.
If this experience does what I hope it does, you’ll leave with more than new ideas. You’ll leave with greater confidence in your own judgment, greater curiosity about what’s possible, and a renewed sense of purpose in the work you do. And perhaps most importantly, you’ll leave knowing that your greatest contribution to the future of software isn’t the code you generate.
It’s the person you’re becoming while you create it.
Who This is for
This experience is designed for professional software developers who want to continue growing as AI transforms our profession.
You might be an individual contributor, senior developer, architect, technical lead, engineering manager, or consultant. What matters most isn’t your title. It’s your desire to build software thoughtfully, continue learning, and help your team navigate change with confidence.
If you’ve been experimenting with AI and wondering how to move beyond prompting toward deeper collaboration, you’ll feel at home here.
Why I Created ACT
Like you, I’ve spent my career trying to become a better software developer.
Over the past thirty years I’ve had the privilege of training more than 10,000 software professionals from organizations including Microsoft, IBM, and Yahoo. I’m the author of Beyond Legacy Code and co-author of Prompt Engineering for Everyone.
What keeps me excited today isn’t AI itself. It’s the opportunity AI gives us to rethink how we learn, collaborate, and grow as professionals. I believe software development has always been about more than writing code. It’s about understanding people, solving meaningful problems, and leaving systems—and one another—better than we found them.
Today my work focuses on helping software developers, teams, and leaders develop the human capabilities that become even more valuable in the age of AI—through thoughtful collaboration, continuous learning, and better ways of thinking together.
ACT grew out of that belief, and I’d be honored to explore it with you.
Testimonials
“Thank you David! You gave me a different way to think about AI and I will be modifying how I interact with it to improve its responses.” — Kortni Kelly
“Really top notch content. I will look for more from David!” — Andrew Sisson
“Great presentation, thanks for the information and for all the passion to share it,” — Gloria Suasnavar
An Invitation
If something in these ideas resonates with you, I’d love to continue the conversation.
I don’t believe every workshop is the right fit for every team, and I don’t think meaningful work begins with a sales pitch. It begins with understanding.
If you’re wondering whether ACT could help your team, let’s schedule a conversation. Tell me about your organization, the challenges you’re facing, and what you’re hoping to accomplish. I’ll share more about how I work, answer your questions honestly, and together we’ll decide whether this feels like the right next step.
If it isn’t, that’s perfectly okay. My hope is that our conversation leaves you with greater clarity, whether we end up working together or not.
Either way, I’d enjoy meeting you.
Every organization is different. Rather than offering a one-size-fits-all solution, I prefer to begin with a conversation. That gives us a chance to understand your goals, explore what’s possible, and determine together whether ACT is the right fit for your team.
FAQ
1. Is this another course about writing better prompts?
“No.”
This is probably the biggest misconception.
We’ll certainly explore prompts, but prompts are only one small part of working effectively with AI. ACT is about developing the human capabilities that make every interaction with AI more thoughtful, intentional, and effective. The goal isn’t to memorize techniques. It’s to become the kind of developer who can adapt as those techniques continue to evolve.
2. I’ve already been using AI every day. Will I still learn something?
Probably.
Many participants already use ChatGPT, Claude, Copilot, or other AI tools extensively. What surprises them is that the biggest opportunities usually aren’t in learning another feature. They’re in seeing new ways to think, collaborate, validate, and design. Those capabilities tend to compound over time.
3. Is this for senior developers or can newer developers benefit too?
The workshop is designed for people who care deeply about building better software.
Some participants have decades of experience. Others are much earlier in their careers. What matters most isn’t how long you’ve been writing software—it’s your willingness to stay curious, learn from others, and think more deeply about your work.
4. What if I’m skeptical about AI?
You’re welcome.
Healthy skepticism is often the beginning of thoughtful learning.
ACT isn’t about convincing anyone that AI is magical or inevitable. It’s about learning where AI genuinely helps, where it doesn’t, and how to exercise sound judgment while working with it.
Some of our best conversations begin with skeptical questions.
5. What actually happens during the workshop?
You’ll experience a blend of short presentations, hands-on activities, small-group discussions, guided reflection, live demonstrations, and collaborative exercises.
Some activities are individual. Others are done with partners or small groups. Throughout the experience you’ll have opportunities to experiment, ask questions, compare perspectives, and apply new ideas to your own work.
The goal isn’t to help you keep up with AI. It’s to help you become the kind of developer who thrives no matter how AI changes.
6. Will I leave with practical techniques I can use immediately?
Absolutely.
You’ll leave with practical habits, exercises, prompts, and approaches that you can begin using the very next time you work with AI.
More importantly, you’ll leave with a framework that continues to help you make better decisions long after the workshop ends.
7. How much preparation do I need?
Very little.
If you’ve been working as a software developer and have experimented with modern AI tools, you’re ready.
Bring your curiosity, your experience, and your questions.
We’ll build from there.
8. What if I’m the only person from my team attending?
You’ll still benefit.
Many participants come individually and discover that hearing perspectives from developers in different organizations is one of the most valuable parts of the experience.
If several members of your team attend together, you’ll also develop a shared language that makes it easier to apply what you’ve learned back at work.
9. What happens after the workshop?
Learning doesn’t stop when the sessions end.
You’ll receive supporting materials, practical exercises, and ideas you can continue applying in your daily work. Many participants also choose to continue the conversation through coaching, team engagements, or future ACT programs.
The workshop is designed to be the beginning of your journey, not the end.
10. How do I know if this is right for me?
That’s a question only you can answer.
If you’ve read this far, there’s a good chance something here has resonated with you.
If you’re curious, if you’re excited by the possibilities, or even if you’re simply wondering how your role as a software developer is evolving, I’d encourage you to trust that curiosity.
I’d be delighted to explore the journey with you.
11. What if I’m ready?
Then schedule a call with me. I’d love to meet you. Whether you’re joining as an individual or exploring ACT for your team, the next step is simply a conversation. We’ll get to know one another, talk about what you’re hoping to accomplish, and decide together whether this feels like the right fit. If it is, wonderful. If it isn’t, I hope you’ll leave our conversation with a few new ideas and greater clarity than when we began.
Either way, I’m grateful you stopped by.