I used to make fun of "vibe coding" and ended up actually doing it. nostr:nprofile1qqsd4dkxqewy8xum47ctpu0ltgxxsfemeewpjkdyzk9ddfcg286s0dsppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9ur9sfc3 told me few weeks ago it works surprisingly well—just letting Copilot and Claude Opus 4 do the work—so I had to try it out. Here's what happened: built this whole thing ( https://www.worldtrip.guide ) from a dataset of maps I've been collecting with friends over the years, without writing a single line of code myself.

The hardest part? Forcing myself not to jump in and fix things. There were so many moments where I'd ask Copilot to move something, watch it completely destroy the layout, then have to resist the urge to dive in. I'd just revert and update those margins manually instead. Often it would dump random chunks of code in weird places that I'd have to track down and delete.

It's honestly like managing a team of overconfident junior developers—incredibly helpful when you're working with tech you don't know well, but watching it mess up stuff you actually understand is genuinely stressful. It's still not for non-tech people though—you need to know where errors are coming from, because it can bounce from one wrong solution to another and back, or just straight up lie to you about what it actually did versus what you asked for.

The real wake-up call came when Copilot crashed and I found myself manually clearing caches to get it working again. That's when it hit me: I really didn't want to go back to fixing all that mess by hand. It's weirdly addictive because you don't want to try to fix all the mess it created yourself.

The trade-off is real though: it's super fast to make a prototype, but gets quite slow when you need an MVP that actually works. It definitely makes me more productive for initial iterations, but the decision not to write code myself ended up slowing me down significantly later.

#AIcoding #copilot #ClaudeOpus #vibecoding #programming #worldtripguide #travelmaps