Vibe coding is harder than engineering You're the: - PM - Designer - Engineer - QA tester Most want it to seem easy, but vibe coding requires an insane attention to detail and curiosity to execute. At the end, you MIGHT have something that works... but it's worth it!

You can find the full video here:

Attention to detail is key in this game. Vibe coding's a whole different beast from engineering. It's like jazz - you gotta feel it, not just build it.

@mattppal, such an interesting take on the complexity of vibe coding!

I think that’s why I love it so much. I studied CS & business and love coding. I became a PM because it was the best thing that kinda checked both boxes but am always frustrated I can’t spend more time just building stuff. Vibe coding checks everything.

idk about that lol we can argue about whether the ceiling is higher, but the floor is WAAAAY lower

True, it requires me to sum it up, break it down, revert to working versions, understand the details of what work and what doesnt because as I mentioned, Replit is like an eager intern. So I need to be very detail oriented. Not to mention different app types require different way

All of that is part of engineering. I've applied a lot of principals of Site Reliability Engineering when developing with Replit. I love that I get to practice all of the skills in such a tight feedback loop because I am in charge of all of it.

It's become kind of a mix like a hobbie and the most stressful task i do during my day. Refuse to join vibe-things, you'll never scape.

💯Agree with you

The annoying thing is that you've finished all the features, and you want to tweak something small but it changes the whole structure