Claude Code seems to be the new shiny object on the frontier for the bleeding edge operators. And I agree, it's kickass.
In this video I'm showcasing a vibe coded tool I've been building. The purpose is simple:
The tool does the following:
- Connects with other APIs and services
- Algorithmically scores 1/ feedback, 2/ voice, 3/ core topics and soon 4/ cadence/frequency
- Externally researches information on core topics
My pro tips when you're vibe coding:
- Plan to spend more time on the FRONT and END of the product cycle
- Be very clear about USER STORIES
- Be very clear about UI / UX
- Be very clear on mobile UI / UX
- DETAIL everything in your specifications
- TIGHTEN UP the details of those specs until you get to a 10/10
- The specs should detail what EXTERNAL SERVICES will leverage
- Prototype any modeled logic externally (I use Python Notebooks to do this)
- Develop an idea for the SCAFFOLDING of your application (what will be in the stack)
- Create a ONE SHOT PROMPT (you will most definitely not one shot complex applications), the PRD, and design instructions (palette, CSS styling, font)
Then you will spend a TON OF TIME iterating. Iterating. ITERATING!
- Create an issue log that auto sends errors in your admin panel
- Create an admin panel
- Develop a table that shows feature gates
- Develop user permissions and roles tied to those feature gates <-- if you've been using Hubspot or Salesforce you should be excellent at this!
Alright I'm done. Thought I'd share a few quick thoughts on Vibe Coding.
I want to vibe buy your app. Please and thank you.
I just hate that the UX of every vibe coded app is virtually identical.
Vibe coding is such an interesting topic! Finding the right energy in our engineering practices can make all the difference.
Impressive Jeff. Love following your content. Tips on setting up your own micro services for a newb?
The toughest challenge isn't writing code—it's figuring out what to build first. Too many founders obsess over technology while ignoring the actual workflow problems.