Herren
619 posts

Herren
@HerrenWeb3
MsC Blockchain Economics WEB3 researcher | WEB2 FinCrime prevention & AI
Katılım Şubat 2024
888 Takip Edilen116 Takipçiler

VIBE CODING 105: Now What? (The Part Nobody Talks About)
You built something. It works. You're staring at it thinking "okay... now what?"
This is where most people stop. They built the thing, proved they could do it, and then it sits unused in a folder somewhere.
Here's what separates people who dabble from people who actually build a portfolio of useful tools:
SHIP IT SOMEWHERE REAL
Not "deploy to Vercel and send the link to nobody." Actually use it. Put it where the problem exists.
- Built a data converter? Bookmark it and use it next time instead of your old method
- Made a dashboard? Set it as your browser home page
- Created a Slack bot? Actually install it in your team's Slack
The code gets better when you're forced to live with it.
SHOW IT TO ONE PERSON
Not Twitter. Not Reddit. One actual human who has the problem you solved.
"Hey, I built this thing that does [X]. Want to try it?"
They'll immediately find the bugs you missed and the features you didn't think of. More importantly: you'll find out if you solved a real problem or an imaginary one.
BUILD THE NEXT THING
Don't spend three months perfecting your first project. Build something new. Take what you learned and apply it faster.
Project 1: Takes two weeks, barely works
Project 2: Takes three days, works better
Project 3: Takes an afternoon, solves the real problem
This is the curve. You don't get good by polishing. You get good by repetition.
THE UNCONVENTIONAL ADVICE:
Delete something every month. Seriously. Look at your projects and kill the ones you haven't touched in 30 days. If you're not using it, you built it wrong or didn't need it.
This sounds harsh but it's liberating. You're not building a museum. You're building tools. Tools that don't get used are clutter.
START RECOGNIZING PROBLEMS DIFFERENTLY
After you've built a few things, your brain changes. You stop accepting annoying manual tasks. You start seeing everything as "I could probably automate this in an hour."
That's when vibe coding clicks. It's not about the code. It's about the problems you can now solve that you used to just tolerate.
WHERE TO GO FROM HERE:
You've got the basics. You know the tools. You've built something. Here's the progression:
Weeks 1-4: Build toys. Simple, single-purpose tools.
Months 2-3: Build something someone else uses. Get feedback. Iterate.
Months 4-6: Build something with multiple features. Deal with state, databases, real complexity.
After that: You're not vibe coding anymore. You're just coding.
THE TRUTH ABOUT VIBE CODING:
It's training wheels. Really good training wheels that let you build real things while you learn, but training wheels nonetheless.
At some point, you'll want to understand what's actually happening. You'll want to write the code yourself because it's faster than explaining it to an AI. You'll want to architect something properly instead of vibing your way through it.
That's not failure. That's graduation.
Use these tools to build things you couldn't build before. Ship them. Learn from them. Break them. Rebuild them better.
And then, maybe six months from now, help someone else get started. Because the best thing about this moment in software development is that the barrier to entry has never been lower.
Your move.
#VibeCoding #ShipIt #BuildInPublic
English

@coolpan967 Nah this is actually not AI. My guy is just being a legend walking on water aswell
English













