DEV Community: okthapian

The Rise of “Vibe Coding” — Fun, Fast… but Dangerous Without Fundamentals

okthapian — Mon, 13 Apr 2026 15:46:33 +0000

Lately, there’s been a new “skill” in the dev world.

Not React. Not Rust. Not system design.

I call it… vibe coding 😄

You open your editor, type something like:

“create a dashboard with charts and filters”

AI responds instantly. You copy. Paste. Maybe tweak a bit.

Boom. It works.

You didn’t fully read it.
You didn’t fully understand it.
But hey… it runs.

And honestly?

It feels amazing.

🚀 The Addictive Part

Let’s be real — vibe coding is fun.

It feels like:

You’re coding at 10x speed
You can build anything instantly
Bugs disappear with a single prompt
You’re basically a wizard now 🧙‍♂️

Got stuck? Ask AI.
Error? Ask AI.
Don’t understand? …still ask AI.

And suddenly, everything feels easy.

⚠️ The Reality Check

But then… reality hits.

Something breaks.

And now:

You don’t know where the logic came from
You don’t understand why it worked before
You don’t know how to fix it

So what do you do?

You ask AI again.

And again.

Welcome to the loop:

“copy → paste → error → ask → repeat”

This is where vibe coding turns from powerful into dangerous.

🧩 The “Simple Error” Trap

Here’s the funny (and scary) part.

Many developers today get stuck on things like:

A missing variable
A wrong parameter
A small logic mistake

Things that would normally take 2 minutes to debug…

Instead turn into:

“Let me ask AI real quick”

This is not efficiency.

This is dependency.

🧠 Why Fundamentals Still Win

In small projects, sure — vibe coding is fine.

But in real-world projects?
The kind that:

Handle real users
Process real money
Scale to thousands of requests

You cannot rely on vibes.

You need to understand:

What your code is actually doing
Why a function behaves a certain way
How data flows through your system
Where things can break

Because when things go wrong (and they will),
AI won’t sit in your production logs with you at 2 AM.

⚖️ The Right Way to “Vibe”

So… should we stop using AI?

Of course not.

That would be like refusing to use Google in 2005.

The real skill today is:

👉 Knowing how to vibe responsibly

Use AI to:

Speed up boilerplate
Explore ideas
Get unstuck

But rely on yourself to:

Verify the logic
Understand the output
Debug the issues

🔥 A Better Mindset

Instead of:

“AI, fix this for me”

Try:

“AI, explain this to me”

Instead of:

“Just give me code”

Try:

“Help me understand why this works”

That small shift changes everything.

💬 Final Thought

Vibe coding is not the enemy.

Blind coding is.

AI is a tool — a very powerful one.

But without fundamentals, you’re not really coding…

You’re just pressing buttons and hoping for the best.

Build fast. Ship faster. But understand everything.

So… be honest 👇
Are you coding… or just vibing? 😏

Helping Small Businesses Get Online — Affordable Website Project

okthapian — Wed, 01 Apr 2026 16:02:11 +0000

Helping Small Businesses Grow with Affordable Websites (Charity Project)

Building a website shouldn’t be expensive.

But for many small businesses, it still is.

That’s why I started a charity-style project to help small businesses get online — without worrying about high costs.

💡 What I Do

I help small businesses build:

Fast and modern websites
Clean and professional landing pages
Mobile-friendly designs
Simple but powerful business websites

From idea → prototype → live website

🎯 Who Is This For?

Small business owners
Local shops & services
Startups with limited budget
Anyone who wants to build an online presence

💰 Affordable Pricing

This is not a typical commercial service.

It’s a support initiative.

Starting from very low cost
Flexible pricing (based on your situation)
Focused on helping, not maximizing profit

🌍 Why I’m Doing This

Many small businesses have great products…

But no website.

No online presence = missed opportunities.

I want to help change that.

🔗 Portfolio

Check my work here:

👉 https://okthapian.github.io/

📩 Let’s Build Your Website

If you’re interested, feel free to reach out:

👉 WhatsApp: https://wa.me/6285606279182

👉 GitHub: https://github.com/okthapian

❤️ Final Note

This project is not just about building websites.

It’s about helping small businesses grow in the digital world.

Tired of Clicking "Add Friend"? I Built a Chrome Extension to Automate It 😄

okthapian — Tue, 31 Mar 2026 16:04:35 +0000

🤯 Tired of Clicking "Add Friend"? I Built a Chrome Extension to Do It

Click… scroll… click… scroll…

That repetitive loop was getting annoying.

So instead of manually sending friend requests one by one, I decided to automate the process — but in a smarter way.

Not a spam bot.

Not something that fires instantly.

But something that behaves more like a human.

⚡ What This Extension Does

This extension helps you:

⏱ Add delay between clicks (min & max interval)
👥 Filter only mutual friends
🔁 Auto scroll and detect new users
📊 Show real-time progress
🛑 Start / Stop anytime

Instead of spamming requests instantly, it mimics human behavior to reduce the risk of restrictions.

🧠 Why Not Just Click Everything Fast?

Because platforms like Facebook monitor suspicious activity.

If you:

Click too fast
Send too many requests
Act like a bot

👉 You might get temporarily blocked.

So this extension uses:

Random delay
Scroll behavior
Progressive interaction

🛠 Tech Stack

JavaScript (Vanilla)
Chrome Extension (Manifest V3)
DOM Manipulation

📦 How to Install

Since it's not on the Chrome Web Store:

Clone the repo:

git clone https://github.com/okthapian/crome_extention_add_friend_fb.git

Open Chrome:

chrome://extensions/

Enable Developer Mode
Click Load unpacked → select the project folder

▶️ How to Use

Open this page:
👉 https://web.facebook.com/friends/suggestions
Click the extension
Configure:

Interval (seconds)
Max add limit
Mutual friends filter

Click:

▶️ Start Adding

📊 Example Output

Progress: 8 (waiting 60s...)

This means it's working — just waiting before the next action.

⚠️ Disclaimer

This project is for educational purposes only.

Use it wisely:

Don't spam
Use delays (≥ 60 seconds recommended)
Limit your daily actions

🙏 Respect the Work

If you find this helpful:

⭐ Star the repo
💬 Give feedback
☕ Or support (internet quota is not free 😄)

🔗 GitHub Repository

👉 https://github.com/okthapian/crome_extention_add_friend_fb

👨‍💻 About Me

🌐 https://okthapian.github.io
💻 https://github.com/okthapian

💡 Final Thought

Automation is powerful — but responsible automation is smarter.

Build tools that help you, not harm your account 😉

Thanks for reading! 🚀

In this article, I’ll show how I built a Chrome Extension that automates Facebook friend requests with delay, filtering, and controlled behavior.

Google Apps Script: Powerful for Learning, Limited for Production

okthapian — Tue, 31 Mar 2026 13:22:06 +0000

Google Apps Script is one of the easiest ways to start building something real with code.

You write a bit of JavaScript, hit deploy, and suddenly you have a working app connected to Google services. No servers, no setup — just pure convenience.

It’s no surprise a lot of beginners (and even experienced devs) get hooked on it.

But at some point, you might start wondering:
“Can I just build everything with this?”

That’s where things start to get interesting.

In this article, we’ll take a closer look at what Google Apps Script is great at — and where it might not be the best choice.

⚡ Why Google Apps Script Feels So Powerful

To be fair, Google Apps Script is incredibly powerful — when used in the right context.

It integrates seamlessly with Google services like Sheets, Drive, and Gmail. You don’t have to think about infrastructure, deployment, or scaling (at least not at the beginning).

⚠️ Where Things Start to Break

The problem isn’t what Google Apps Script can do — it’s how far people try to push it.

As your app grows, you’ll start running into limitations: execution time limits, slower performance, and a lack of flexibility compared to traditional backends.

What works perfectly for a small script or internal tool can quickly become frustrating when more users, more data, or more complexity are involved.

At that point, things don’t scale as smoothly as you might expect.

🚫 It’s Not a Full Backend (And That’s Okay)

Google Apps Script was never meant to replace a full backend framework.

It doesn’t give you the same level of control, performance, or scalability you’d get from something like Node.js or other backend solutions.

And that’s completely fine.

The issue only starts when we expect it to do everything.

✅ When It Actually Makes Sense to Use It

Despite its limitations, Google Apps Script is still a great choice for many use cases:

Automating repetitive tasks
Working with Google Sheets as a lightweight database
Building internal tools
Creating quick prototypes or MVPs
Personal projects

In these scenarios, it’s fast, simple, and incredibly effective.

🚀 A Smarter Way to Use It

Instead of forcing Google Apps Script to handle everything, a better approach is to use it where it shines.

For example, you can use it as a lightweight API or automation layer, while keeping your main application on a more robust stack.

This way, you get the best of both worlds — simplicity where you need it, and scalability where it matters.

🔥 Final Thoughts

Google Apps Script is powerful — but only when used wisely.

It’s an amazing tool for learning, building small projects, and getting things done quickly.

But for larger, production-level applications, choosing the right tools early on can save you a lot of time and frustration.

At the end of the day, it’s not about what a tool can do — it’s about what it’s meant to do.

You can go from idea to working prototype in minutes.

For automation, internal tools, or quick experiments, it honestly feels like a superpower.