Skip to content

Connect

Convert Developer AI Assistant Frustration into Engineering Breakthroughs

Your developers' AI assistant struggles aren't unique, but the solutions can be empowering. After helping CTOs convert their developers from AI assistant frustration to reliable productivity, I've learned that the best insights emerge when engineering leaders share real experiences: both failures and breakthroughs.

Why Connect?

Every conversation generates new insights for both participants. Whether you're struggling with AI adoption, discovered your own agentic engineering practices, or leading engineering communities, our exchange will likely benefit us both.

What you're experiencing could spark my next breakthrough. What I've discovered might solve your current challenge.

Let's Connect and Innovate Together

  • Enterprise Leaders & CTOs

    What You're Experiencing:

    Your developers tried AI assistants. Results are inconsistent. Some developers converted them off. Others generate code that makes you cringe. The developer productivity promises aren't materializing.

    What I've Learned:

    Through 20+ years of engineering leadership and thousands of hours helping developers with AI, I've discovered agentic engineering practices that convert this exact developer frustration into reliable productivity.

    Let's Explore Together:

    • Share insights from agentic developer AI implementations that actually work
    • Understand what engineering principles look like for developer AI-assisted development
    • Explore practices that preserve code quality while increasing sustainable developer productivity
    • Learn from each other's experiences with developer AI empowerment and satisfaction

    Let's Connect Transform Your Team

  • Conference Organizers

    Your Need:

    Fresh perspectives on AI that go beyond hype. Speakers who can engage both technical teams and executives with real-world agentic engineering practices.

    My Practices:

    Real experiences from thousands of hours of AI-assisted development. Not theoretical frameworks, but agentic engineering practices that convert daily development practice into reliable engineering excellence.

    Popular Topics:

    • From AI Frustration to AI Acceleration (workshop format)
    • Engineering Excellence for AI-Assisted Development
    • Why 82% Use AI But Only 28% Trust It
    • Agentic Engineering Practices for Enterprise Teams

    Book Speaking View Topics

  • Fellow Practitioners

    Your Discovery:

    You've found agentic engineering practices for developer AI-assisted development that actually work. You understand the difference between random prompts and engineering excellence that delivers consistent developer results.

    Let's Exchange:

    The best insights emerge when different agentic engineering practices collide. I'm always learning from practitioners who've found their own breakthrough techniques for developer empowerment and can share real implementation experiences.

    What We'll Discuss:

    • Compare agentic developer practices and their effectiveness
    • Share developer implementation challenges and breakthrough moments
    • Explore how different organizations achieve developer AI-assisted development success
    • Build community around validated developer engineering practices

    Share Ideas

Building the Agentic Software Engineering Community

Mutual Learning Philosophy

Every conversation generates new insights for both participants. Whether you're just starting your AI journey or you've discovered your own breakthrough techniques, our exchange will likely benefit us both.

What connects us: The shared experience of moving beyond random AI prompts to agentic engineering practices.

Agentic Software Engineering Practitioners Network

Growing community of CTOs, engineering leaders, and practitioners who are implementing structured AI development practices in their organizations. This network focuses on sharing real experiences, validated techniques, and practical insights about enterprise AI adoption.

Community focus areas:

  • Tested agentic engineering practices and their real-world application
  • Developer empowerment from AI skepticism to AI advocacy
  • Enterprise implementation strategies and lessons learned
  • Quality maintenance while scaling AI-assisted development
  • Security-first AI deployment patterns

Access through work-together programs ensures community members are serious practitioners with genuine implementation experience, not theoretical discussions.

Explore the Foundation

Want to understand the agentic engineering practices before connecting?

Social Connections

While I'm active across various platforms, the best conversations happen when we move beyond 280-character limits:

My Framework for Connection

I believe in meaningful exchanges over rapid-fire exchanges. Expect thoughtful responses rather than immediate ones. Quality conversations about AI-assisted development take time to develop properly.

The goal isn't networking - it's building Agentic Engineering community. Real conversations that generate new insights about AI-assisted development for both of us.

What Makes Great AI-Assisted Development Conversations

  • Specific examples over abstract theories
  • Failed experiments are as valuable as successful ones
  • Teaching moments where we both learn something new
  • Practical insights that can be applied immediately
  • Community building that helps others discover these practices

Start a Great Conversation

The best emails I receive often start with: "I tried your agentic engineering practices and here's what happened..." or "I discovered a different technique for X and thought you'd find it interesting..."

Share your real experiences - both successes and failures teach us all.

Frequently Asked Questions

Questions about connecting and networking? Here are answers to help set clear expectations:

What kind of time commitment is involved in connecting?

Quality over quantity. I prefer meaningful exchanges over rapid-fire interactions.

Typical interaction patterns:

  • Initial conversations: 30-60 minutes for substantial exchange of ideas
  • Follow-up discussions: As needed based on mutual interest and value
  • Community building: Ongoing but not demanding
  • Speaking opportunities: Scheduled around your event needs

The goal is building lasting relationships around AI-assisted development, not networking for networking's sake.

Do you share sensitive business information in these conversations?

Professional discretion is fundamental. All conversations respect confidentiality and competitive sensitivity.

My practices:

  • Focus on principles and frameworks, not proprietary implementations
  • Share general patterns without company-specific details
  • Always ask before referencing our conversations publicly
  • Respect NDA requirements when they exist

We can explore agentic engineering practices without revealing competitive advantages.

How do you handle conversations with competitors or overlapping markets?

The AI-assisted development space is large enough for multiple practices. Competition in frameworks drives innovation for everyone.

My philosophy:

  • Different agentic engineering practices work for different contexts
  • Learning from various frameworks benefits the entire community
  • Rising tide lifts all boats - better AI-assisted development helps everyone
  • Focus on advancing the field rather than protecting territory

The best conversations often happen between practitioners with different but complementary practices.

What's my view on intellectual property and framework sharing?

Open sharing of principles, protective of specific implementations. I believe AI-assisted development improves when practitioners share foundational insights.

What I share freely:

  • Core principles and practical frameworks
  • General patterns that work across organizations
  • Learning from successes and failures
  • Community building and knowledge advancement

What stays proprietary:

  • Client-specific implementations and context
  • Detailed AI proficiency programs and curricula
  • Specific assistants and templates developed for particular engagements

The goal is advancing the field while respecting commercial realities.

How do you evaluate whether a conversation will be mutually valuable?

The best conversations start with specific experiences - either challenges you're facing or breakthroughs you've discovered.

Signals of valuable exchange:

  • You've tried agentic engineering practices (successful or not)
  • You have specific questions about implementation
  • You've discovered techniques I haven't considered
  • You're solving similar problems with different practices
  • You're building community around these practices

The richest conversations come from practitioners with real experience to share.

Ready to Connect?

Next Steps

Understanding the Foundation: Before reaching out, explore the practices behind AI-assisted development. This helps ensure our conversation adds value for both of us:

Practice Overview: Agentic Engineering Practices - Understand the practices behind the results

My Journey: Full Story - 20+ years of engineering leadership progression

Speaking & Ideas: Conference Talks - See the practices in action

Working Together: Transform Your Team - Discovery sessions, workshops, and AI proficiency programs

Ready to Connect: Share Your AI-Assisted Development Experiences - Start the conversation

The best insights about AI-assisted development emerge when practitioners share real experiences: both successes and failures. Every conversation teaches us something new.