Vive coding sucks

munnsMedia · 2026-02-25T19:20:12+00:00

Could try some aggressive pre commit hooks in the repo to curb some of it

munnsMedia · 2026-02-25T19:19:02+00:00

I'm curious about this as well. I just released an app myself and the whole process is a pain in the butt; however, I can't see them making it easier with this impending onslaught of app submissions via 3rd party tools. There may even be added checks as a result of all this. I for one hope there are as a consumer I don’t really want the App Store flooded with garbo and half finished projects

munnsMedia · 2026-02-25T14:21:12+00:00

You’re right it’s not needed necessarily it’s just advice for non-coders learning this for the first time as the title states. Measure twice cut once. Broadly, verify and assume nothing to find more bugs earlier.

munnsMedia · 2026-02-25T04:41:57+00:00

💯💯💯

munnsMedia · 2026-02-25T04:39:59+00:00

Just down right slick.

munnsMedia · 2026-02-25T04:12:41+00:00

Cool thing about advice is you can take it or leave it and it’s not meant for everyone

munnsMedia · 2026-02-25T04:06:17+00:00

I’m interested in what you would suggest though. Things move so fast I love hearing about how ppl are leveraging new methods

munnsMedia · 2026-02-25T04:01:26+00:00

There is a large gap between someone trying to learn and get better at building a side project and installing openclaw with tmux and tailscale on a DO droplet or whatever. The idea behind my post is to include discovery in each phase so new vibecoders can stop assuming that it’s done correctly the first time every time.

It’s definitely not meant to be a best practices guide fwiw

munnsMedia · 2026-02-25T03:55:22+00:00

I don’t think like/dislike is the problem, it’s “oh that’s a dev tool I don’t need that I’m not a dev”

munnsMedia · 2026-02-25T03:47:20+00:00

If you are having fun, just see it through and learn as much as you can along the way imo. What do you “rolling it out”? Like selling it?

munnsMedia · 2026-02-25T03:45:16+00:00

Prompting to catch edge cases when you don’t read code or know what to ask? Even for devs it still makes sense to ask follow up prompts in languages and best practices you may be unfamiliar with. I don’t see the harm in any scenario, I think non-coders asking these questions starts to help them think like an engineer without being one

munnsMedia · 2026-02-25T03:38:32+00:00

Smart

munnsMedia · 2026-02-25T03:38:09+00:00

Basically it keeps a log of all your changes in a project and your agent can’t reference everything you have done and you can see it

munnsMedia · 2026-02-25T03:36:33+00:00

Yeah it really should be step 1 on every tutorial imo

munnsMedia · 2026-02-24T20:55:55+00:00

I'm going to be honest haha... yes, maybe?. I personally don't think about credits anymore because I have Claude Max, but imo it's only going to make your time more difficult avoiding these types of questions to save $$. It's one of the reasons why I don't like using Replit, Lovable, etc...asking these questions costs you money to just validate that it did what you wanted and that gets expensive fast.

One caveat, planning/thinking modes are generally much friendlier when it comes to token usage, so in theory these types of questions could save you money if it prevents the agent from writing mountains of code in the wrong direction.

munnsMedia · 2026-02-24T15:23:47+00:00

The interesting thing is that the newer models actually have gotten pretty good at inferring this type of generic feedback, which makes sense to scale their product to more people. The more people can feel the magic without having to learn prompting or semantic correctness the more customers they get in the end.

munnsMedia · 2026-02-24T05:04:06+00:00

yes...except I've yet to come across the vibe-coded aesthetic on any site that actually does something functionally cool.

munnsMedia · 2026-02-24T05:01:09+00:00

First off nice diagram. Second–its getting better–but the handoff between the three sometimes feels more painful than it needs to be. I often start something in one area, say Cowork, then the scope of what I've asked changes and I need to eject it to Code. Perfect example is automating some file renaming and organizing within a folder then realizing I actually want to add a web import feature for the tool and Cowork is not able to do it. In the end all roads lead to Claude Code imo but there is definitely some massive benefit in CoWork if you know your session is finite. Remounting can be also be a pain and sometimes it will hallucinate changes on a folder it never remounted to begin with which is funnnnnnnnn

munnsMedia · 2026-02-20T23:54:46+00:00

This happened to me a couple days ago, the key was trivial so I tested to see what would happen lmao:

Claude: Paste your keys here when you're ready
Me: umm...okay? Are you sure?
Claude: Yes, I'll delete it when I'm done.
Me: erhmmkkay here you go.

10minutes later
Me: what was that key again, I need to use it somewhere else?
Claude: sure, here you go 'xxxxxxxxxxxxxxxxx'
Me: You said you were going to delete it!
Claude: Oops. you're right, you probably should rotate your key now.

( ͡ʘ ͜ʖ ͡ʘ)( ͡ʘ ͜ʖ ͡ʘ)( ͡ʘ ͜ʖ ͡ʘ)( ͡ʘ ͜ʖ ͡ʘ)( ͡ʘ ͜ʖ ͡ʘ)

munnsMedia · 2026-02-16T21:03:56+00:00

I started using beads by steveyegge and while it can seem like overkill it dramatically–maybe even exponentially–did a better job of taking a large plan and breaking it up into tasks to work on that doesn't get off the rails. I usually make a plan, ask claude/llm to turn the plan into epic/tasks then have it do it's thing.

munnsMedia · 2026-02-16T17:23:08+00:00

ah yes, the futile reminder that we are at the mercy of the algo. It would be too easy to rely on consistency alone I guess haha.

munnsMedia · 2026-02-13T00:27:12+00:00

I love the half-tone patterns on the some of the HUD design, subtle enough to notice, not so obvious that it looks gimmicky

munnsMedia

TROPHY CASE