Are you struggling with vibe coding?
This post is inspired from
I write this not to be mean, not to sound patronizing, but I write this to give perspective.
We are building software.
When I first started building software at 12, there were times I would be stuck on the same problem for days.
It would require me to review the code line by line.
Read forums, go to Reddit, make a Stack Overflow post.
Then go back to that exact same problem and try again.
We are talking 10+ hour days on the same problem.
At some point, the eureka effect would happen, and I would solve it.
But only after X amount of days working on it.
I say this for you to realize that if you are getting frustrated after just one day of bad code outputs, try two weeks on the same problem.
Learning compounds, so I can guarantee you, , if you stick to it, those same annoying and bad code outputs you receive now will be a walk in the park one year from now.
Perspective.
The same thing that would have taken me a week to code in the past, 7 days, now takes me three hours.
AI is such an accelerator now that I was able to build out enterprise level software in eight weeks.
200K lines of code.
Lean in now, learn the skill now.
28
23 comments
Corbin Brown
6
Are you struggling with vibe coding?
Builder’s Console Log 🛠️
skool.com/ai-for-your-business
We build things because it’s fun.
console.log ("democratize developing");
Leaderboard (30-day)
Powered by