AD
Episode
379
Interview
Web News

What Happens When a Real Developer Starts Vibe Coding?

Recorded:
June 5, 2025
Released:
June 17, 2025
Episode Number:
379

What happens when a real developer uses AI to build something in a language and toolset they’ve never touched before? In this episode, Matt shares the story of how he created a free, custom-coded Google News sitemap generator using Node.js, GitHub Actions, and the Webflow API—with help from AI. The catch? He had no prior experience with any of those tools.

Listen

Also available on...
...and many more, check your podcast app!

Who’s in This Episode?

Show Notes

The Big Question

What’s the step above vibe coding? Is it still vibe coding?

Introduction

  • Vibe coders - or at least the meme of a vibe coder - is someone that is coding up a project entirely AI without any programming knowledge.. so of course chaos and weird issues arise due to inexperience
  • What happens though when a programmer doesn’t intentionally go to “vibe code” but instead uses AI to code up something new to them

Personal Example

  • I recently needed to create a google news sitemap
    • Had to update once daily
    • Needed to be completely free (hosting and all)
    • Could not host it on the same server as the website that it serves
    • Needed to be custom coded in order to be free - tried Make and Zapier but kept bumping up against limitations on their free plans
    • This was for a Webflow website, so I needed to use the Webflow API (or scrape, but API seemed to be the best solution according to my research)
  • So I “vibe coded” a solution on GitHub using GitHub Pages & Github Actions using node.js
    • I’ve never used node.js before
    • I’ve never used Github Pages or GitHub Actions before either
    • I haven’t attempted to use the Webflow API before, but have used other APIs in the past
    • ChatGPT was able to:
      • Help me write the code
      • Get the repo set up on GitHub
      • Help with troubleshooting issues and test cases
    • ChatGPT was not able to:
      • Figure out that we were barking up the wrong tree - we got stuck for a while and I realized that we were coding in APIv1 when we needed to be coding in APIv2 - When I realized this I sent ChatGPT the info it needed and then it corrected the code and everything else around it (but the bot was unable to figure out this as a troubleshooting step)
      • Realize that publishing an API publicly is never a good idea and that even though it was read only on public data - I created a second key and then deleted it (we were troubleshooting so needed to hardcode an API key temporarily for a few minutes)
      • Realize that the API data was not being indexed properly - I went and checked what the raw payload was, realized that ChatGPT was reading it improperly, sent in the new structure and then Chat fixed itself

Links




How to support the show

Patreon

Prices subject to change and are listed in USD

  • Support the show from as little as ~$1/month
  • Get a shoutout at the end of the episode (while supplies last) for just ~$3/month
  • Help support the HTML All The Things Podcast: Click Here

Scrimba Discount - Coding Courses!

Learn to code using Scrimba with their interactive follow-along code editor.

Join their exclusive discord communities and network to find your first job!

Use our affiliate link for a 20% discount!!

  • Click the link to take you to the Scrimba site
  • A pop-up should appear on your screen with the discount amount and instructions on how to claim it
  • Discount is for new accounts only

We receive a monetary kickback if you use our affiliate link and make a purchase.