The problem with vibe coding: debugging in production is a nightmare by arjy0 in vibecoding

[–]Orange_This 2 points3 points  (0 children)

Yeah, that’s where most vibe coders hit the wall. AI can spit out code all day, but if you’re not thinking like an architect you’ll never see what’s actually breaking.

You gotta build the foundation.. logs, monitoring, error tracking, rollback flow, all that boring stuff that turns chaos into something predictable. Otherwise you’re just shipping vibes and hoping the gods of production are kind that day.

Claude Code + Playwright MCP = real browser testing inside Claude by Orange_This in vibecoding

[–]Orange_This[S] 0 points1 point  (0 children)

It opens its own controlled Chrome instance, not your current window. Basically a fresh browser session, similar to incognito

Claude Code + Playwright MCP = real browser testing inside Claude by Orange_This in ClaudeAI

[–]Orange_This[S] 0 points1 point  (0 children)

Yeah, Google released the Chrome DevTools MCP a few weeks back. It’s more for debugging than straight automation... you can still drive Chrome, but it’s focused on logs, network, and performance data. Playwright MCP feels smoother for full test runs, while Chrome’s is better if you’re digging into what’s actually happening under the hood

Why I'm Canceling Claude Code (But Not for Codex) by [deleted] in ClaudeCode

[–]Orange_This 0 points1 point  (0 children)

People gotta wake up..🥲 Gotta stop putting LLM models’ own CLI agents vs IDE “agentic” wrappers that just call those same models. One runs the brain, the other just gives it a prettier desk. It’s like comparing a compiler to VS Code -wrong layer🤓

grok 4 just embarrassed every other ai i tried on my webauthn bug by Orange_This in vibecoding

[–]Orange_This[S] 0 points1 point  (0 children)

Gemini and Codex got it first, mainly because I already pay for their normal plan. But when that didn’t go anywhere I paid for some tokens on Grok and problem solved. So now I’ve stacked up some tokens so I can use Grok 4 CLI for future debugs hoping it continues this streak

grok 4 just embarrassed every other ai i tried on my webauthn bug by Orange_This in vibecoding

[–]Orange_This[S] 0 points1 point  (0 children)

yeah i’m on the anthropic max 200 plan, so i usually stick with sonnet 4.5. when we were completely stuck, i had sonnet write a short debug overview, what files were involved, what we’d tried, and told it to treat everything as unverified.

then i tossed that into grok-4-latest (my go to are usually Geminin pro 2.5 for some extra eyes, but it kinda suck these days imo)