The ChatGPT Experiment – Ep 102: A Simple Explanation of Agents and Vibe Coding with Greg Howe

Date: March 21, 2026
Host: Cary Weston
Guest: Greg Howe (Founder, Gimme Info LLC)

Episode Overview

In this episode, Cary Weston brings Greg Howe back to demystify two important yet often-misunderstood AI concepts: agents and vibe coding. Aimed at curious beginners, Cary and Greg break down these terms using real-life analogies and plain language, offering listeners foundational understanding without deep technical jargon. The conversation is focused on empowering professionals and enthusiasts to feel comfortable with these concepts, know when and why to use them, and understand their growing role in practical AI solutions.

Key Discussion Points & Insights

1. Why These Topics? (03:31–05:30)

• Cary explains why terms like “agents” and “vibe coding” often confuse people—even those who use AI tools regularly.
• Many newcomers feel pressured to already understand AI terminology.
• The aim: offer “water cooler” conversational clarity, not a technical tutorial.

Quote:
“There's a lot of folks that use words and terms that we're thinking we're supposed to know... but oftentimes we don't.” — Cary Weston (04:10)

2. What Is an “Agent”? (06:39–16:00)

a. Simple Definition (07:32–08:52)

• Greg’s 101 Explanation:
  An agent is an AI 'employee' (or ‘contractor’) with a singular job. It takes an input, does its job, and gives an output.
• Agents can “talk” to each other—one agent’s output can feed into another.

Quote:
“The idea of an agent is kind of what you would consider to be an AI internal. An agent has a job and you go say, here, here's some input. Go do your job and produce some output and let me know when you're done.” — Greg Howe (07:35)

b. Agent vs. Custom GPT (09:14–10:04)

• Custom GPTs are ChatGPT instances with specific instructions—essentially, focused, purpose-driven agents.
• Agents: job-focused, input→process→output.

Quote:
“What makes it an agent is that it has an input, it has a job to do, and it has an output.” — Greg Howe (09:35)

c. “Contractor” Analogy & Decision-Making (10:12–11:35)

• Agents can apply logic and make simple decisions (e.g., skip a step if not required).
• Like a plumber with tools: you state a problem, they determine how to fix it.

d. Where Do You Find Agents? (12:09–13:17)

• No “agent marketplace” yet—most agents today are built for specific needs.
• Start from your business problem, not from the tech.

e. Step-by-Step Guidance for Beginners (14:55–19:27)

• Open ChatGPT (or similar tool), explain your problem in plain language, and ask if an agent would help—request consultation, not just code or tool suggestions.
• Focus on the business use-case first before diving into AI specifics.

f. Summary Checklist for Beginners (18:23–19:27)

• Use AI tools as consultants.
• “Find your one thing”—start with a single business pain point.
• Agents can be stacked/reused for different problems.

Quote:
“Once you have an agent that does a good job... it can also be used for other problems that you might want to solve. So these agents are reusable. You stack them differently.” — Greg Howe (19:53)

3. What Is “Vibe Coding”? (21:03–35:21)

a. What Does "Vibe Coding" Mean? (21:03–22:32)

• Vibe coding: describing what you want in plain English, letting AI write the code, and then iterating based on your feedback.
• Works for both visual and functional programming.

Quote:
“You describe what you want in plain English, AI writes the code, and then it becomes this iterative process where you say you want to change something and it changes it.” — Greg Howe (21:03)

b. Real-World Examples (22:13–25:07)

• Greg built an entire SaaS product via vibe coding—never wrote a line of code, just iteratively instructed the AI.
• Monday.com Case: Developers cloned Monday.com’s core features in about an hour by describing the site to AI.

Quote:
“I never wrote a single line of code. The entire thing was vibe code. And it works beautifully and it's better than I would have written it.” — Greg Howe (22:13)

c. Practical Application for Small Businesses (24:23–25:07)

• Even non-tech professionals could build custom solutions by conversing with AI instead of paying monthly SaaS fees.
• Caveat: start with solving one pain point at a time.

4. Caveats and Limitations of Vibe Coding (25:07–29:29)

a. Manage Expectations

• Don’t expect perfection in the first iteration—AI code/output quality varies.
• Save work in pieces, backtrack as needed.
• AI can “forget” earlier parts of conversations in long sessions (“the backpack gets full”).

Quote:
“Understand that what it generates can sometimes be crap. It shouldn’t turn you away from it... just say to it, that was crap. Do it. I want this to be more professional.” — Greg Howe (25:18)

b. Don’t Be Afraid to Direct the AI

• AI won’t push back if your instructions are unclear—it does what it’s told, sometimes incorrectly if you’re vague.
• Give visual/business context, examples, and feedback.

5. Universal ChatGPT Principles in Practice (29:41–34:35)

• Role-play with AI tools: assign them roles (developer, architect, advisor), have them ask clarifying questions, and let them interview you to understand needs.
• Build prototypes and have AI produce “blueprints”—even outside of software (e.g., house plans).

Quote:
“You want to tie in the other part. Create an agent that is your architect. Create an agent that is your senior developer... that doesn’t build code for you, but tells you here are the gaps.” — Greg Howe (33:06)

Notable Quotes & Memorable Moments

• On Agent Simplicity (07:35):
  “An agent has a job and you go say, here, here’s some input. Go do your job and produce some output and let me know when you’re done.” — Greg Howe

• On Vibe Coding (21:03):
  “You describe what you want in plain English, AI writes the code, and then it becomes this iterative process where you say you want to change something and it changes it.”

• Caveat for Beginners (25:18):
  “Understand that what it generates can sometimes be crap. It shouldn’t turn you away from it... That’s the whole vibe aspect.”

• AI as a Business Consultant (13:17):
  “If an agent makes sense to solve the problem at hand, then you would have to go use... whatever tool you like, and start saying, hey, I’m looking to create an agent that can do this task for me.”

Timestamps for Key Segments

• 03:31 – Introduction of confusion around agents and vibe coding
• 05:30 – Greg’s introduction and approach to AI for small businesses
• 07:32 – 101 definition and analogy for agents
• 09:14 – Agents vs. Custom GPTs
• 10:12 – Difference between "tool" and "agent" (contractor analogy)
• 12:09 – Where agents come from, building your own
• 14:55 – How to approach AI tools as a beginner
• 18:23 – Checklist summary for identifying/using agents
• 21:03 – What is vibe coding
• 22:13 – Greg’s SaaS built via vibe coding; the Monday.com example
• 25:18 – Critical caveats for beginners using vibe coding
• 29:41 – Leveraging core ChatGPT practices for agents/vibe coding
• 33:05 – Role-playing and productive AI consultation
• 36:17 – Greg’s contact details and his experience with vibe coding

Conclusion & Takeaways

• Agents: Think of AI agents as single-task contractors. Focus on defining the problem; let them do the task—and perhaps talk to each other. Build or reuse as needed.
• Vibe Coding: Use plain language to describe needs and iteratively refine the AI’s results. Start small and expect several rounds of feedback.
• For Beginners: Don’t start with AI—start with your business problem. Have simple, back-and-forth conversations with AI tools. Use analogies and role-play to structure your exploration.
• Final Thought: Stay curious—comfort and capability with AI grows out of small, practical steps rather than trying to understand or implement everything at once.

Connect with Greg Howe

• LinkedIn: Greg Howe / Gimme Info
• Email: greg@gimmee.info
• Website: gimmee.info

“Get your hands dirty, but understand it’s just like the contractor mentality: there’s a lot you can do, but sometimes you need a professional.” — Greg Howe (37:03)