Skip to main content
Skip to content
Menu

vibe coding Intermediate 4 parts Updated

Pitch disciplined AI development to your team

You'll have a 5–10 slide presentation that contrasts fast-and-loose prototyping with professional AI-assisted workflows, plus concrete steps your team can adopt starting this week.

What you'll make

Agentic Engineering Pitch Deck

  1. Slide 1: The problem we're solving (examples from our codebase)
  2. Slide 2: What vibe coding actually costs us (time, bugs, technical debt)
  3. Slide 3: Agentic engineering defined (the professional alternative)
  4. Slide 4: The workflow difference (side-by-side comparison)
  5. Slide 5: Testing as the forcing function (why this matters most)
  6. Slide 6: Three changes we implement this week
  7. Slide 7: Expected pushback and our response
  8. Slide 8: Success metrics (how we'll know it's working)

Upload screenshots of your 5-8 slide deck with speaker notes included

The 4 parts

Each part ends with a check you can see.

  1. Document Your Vibe Coding Reality

    Inventory actual examples of chaotic AI coding from your team's recent work to establish the problem.

    Done when

    You have 3-5 concrete examples of where vibe coding created problems in your team's actual codebase, with specific costs (time spent debugging, bugs shipped, technical debt created).

  2. Map Agentic Engineering for Your Team

    Design the specific workflow changes that would prevent your documented problems.

    Done when

    You have a side-by-side comparison showing current vibe coding workflow vs proposed agentic engineering workflow, with 3-5 specific practice changes your team can implement immediately.

  3. Prepare for the Speed Objection

    Develop responses to the inevitable 'but vibe coding is faster' pushback with evidence about long-term velocity.

    Done when

    You have scripted responses to the top 3 objections your team will raise, backed by evidence from your problem audit and workflow analysis.

  4. Assemble Your Pitch Presentation

    Create the slide deck that tells the complete story from current problems to proposed solutions.

    Done when

    You have a complete 5-8 slide presentation with speaker notes that flows from problem evidence through proposed solutions to implementation plan.

    Capstone: you put together your Agentic Engineering Pitch Deck.

Where this helps

An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.

About this lesson

What you'll be able to do

  • Deliver a compelling presentation that contrasts vibe coding with agentic engineering using your team's actual codebase examples
  • Propose 3-5 specific workflow changes your team can implement this week to shift from ad-hoc AI use to disciplined practices
  • Handle the 'but it's faster to just prompt and ship' objection with concrete evidence about long-term velocity and quality

Who it's for

  • Engineering team leads who've seen AI coding turn chaotic and want to introduce discipline
  • Senior developers tasked with establishing AI development standards for their team
  • CTOs or engineering managers who need to pitch structured AI workflows up to leadership

What it won't cover

  • Specific AI coding tools or model comparisons
  • Writing comprehensive test suites from scratch
  • Company-wide AI governance policies
  • Technical implementation details of agentic workflows

Skills you'll practise

  • Evidence-based differentiation between development approaches
  • Workflow design for AI-assisted engineering teams
  • Stakeholder communication about engineering practices
  • Risk assessment of AI development approaches