Git ⢠REST APIs ⢠Unit Testing ⢠AI-Assisted Development (Cursor, Cloud, GitHub Copilot)
šØāš» About Me About Me
I'm a Full-Stack JavaScript Developer with approximately 4 years of experience in web application development. I've worked on a variety of projects, including:
SaaS Platforms
Task Management Systems
E-Commerce Platforms
Business Dashboards
Booking Platforms
Medical Websites
Custom Business Solutions
My goal is for you to receive a professional, scalable, and easy-to-maintain product, not just a website that looks good.
clean layout, the story cards read well. does the admin side have drafts and scheduled posts? that's usually the first thing people ask for once they start writing regularly
Vibe coding looks easy⦠until your app breaks. š
āJust tell AI what you want and it will build it.ā
Sounds great.
Until you spend credits asking it to fix the same bug 10 different ways.
Then another feature breaks.
You fix that one.
Something else stops working.
Then you're staring at the same error for hours thinking:
āWhy is this still happening?ā
That's the part people don't show you about vibe coding.
AI can write code incredibly fast, but fast code doesn't automatically mean good code.
You still need to understand:
ā How the application is structured
ā Where the bug is actually coming from
ā How different features affect each other
ā When an AI-generated solution is making things worse
ā How to debug instead of blindly regenerating code
And sometimes the biggest time killer isn't building a feature.
It's getting stuck on one tiny bug that refuses to die.
That's why I don't see vibe coding as:
āTell AI what to build.ā
I see it as:
Human problem-solving + AI development.
The AI can help you move faster.
But you still need someone who knows where to go when things stop working.
That's where the real skill comes in.
What has been your biggest headache with vibe coding? š