this post was submitted on 18 Sep 2026
127 points (97.0% liked)
Programming
29135 readers
489 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Professional coder turned vibe coder here. My approach has been to lean in really heavy on creating deterministic harnesses and guardrails, that can also be templated for bootstrapping new slop projects quickly and easily.
Then I end up just getting paid to press button make feature go brrrr, and on my other monitor I work on personal projects that I actually care about, while simultaneously being paid because I press button make feature go brrrr.
Spending the time curating my harnesses and workflows, including pretty rigorous automated testing of what Claude shits out, is what keeps it all together. You can't just set it and forget it. Something about that is fun to me, though, because I am masochistic devops man.
Seems like vibe coding is now all about setting up gard rails for the chatbot, which does not sound remotely fun to me compared to actually writing the code.
You're not wrong, and to each his own. I'm a workflow and automation nerd, so it's down my alley personally.
Thanks for sharing your workflow. I'm already pretty fed up on how tech just keeps on adding layers upon layers of complexity. I love understanding what goes on. You can imagine I'm not thrilled.
These people are the ones causing the problems. They tell you they've got it all figured out make it sound great but they're the ones shitting out garbage faster than you can fix it.
If you're gonna talk shit about my skills you could at least @ me. I've worked decades in the industry, with a lot of that time knee-deep in dev tooling and devops. It's a cake walk keeping an LLM on guard rails producing well-tested code if you're a seasoned and sane architect, compared to say, humans. Sorry you can't seem to wrap your head around it.
Lol
That doesn't mean anything. I have seen senior developers who built up "street cred" for decades fall into the vibecoding trap and deskill themselves rapidly.
Wow, you sound insufferable.
Congratulations on giving up your career, though. I'm sure the "architect" will take care of you.
I'm not sure how you gathered I gave up my career. I adapted to the trend, and now make more money with less effort. And when the wind changes, I'll adapt again, until I'm put out to pasture.
That's pretty great actually!
I've so far managed to avoid being mandated vibe coding at work since I have some pull at the company, so I don't have a ton of experience working with it.
How long does each brrrr take? Does it give you a reasonable amount of time to sink into a personal project before it completes?
I have hand-rolled agents/skills that run through a standardized process:
I leverage bash and python scripts whenever possible within harnesses, to try to avoid Claude injecting flair where steps and processes should be as repeatable as possible. I also write a lot of supplementary skills for it to use, with least-privilege scoping (important!), to give it access to do things like read work request tickets, run staging smoke tests, etc.
You can get to a point where you can basically say something like, "Investigate and plan SWE-1773" and it'll do all the shit, spit out a human-readable markdown plan complete with mermaid diagrams. You then okay to execute it, and at the end do an earnest PR review, and some manual tests.
Each brrr is gonna depend on how thorough you need to be, feature sizes, and if it shits the bed during planning. But honestly, the likelihood of your LLM shitting the bed is heavily dependent on how good of a harness engineer you want to become. If you shape and mold the environment and workflow like someone who say, works in developer tooling, then output quality can become surprisingly reliable.
You said you work on personal projects while it brrrrs. Of course it depends, but are we talking personal projects 30s at a time, 10 min at a time, or an hour?
I'd say that in an ~8hr workday, an average of 60-70% of my workday is spent doing stuff I want to do.
I can't comment on cadence. Protip is to leverage git worktrees, multiple Claude session, and then spin up multiple feature requests at a time. This maintains "productivity" expectations and gives you longer spans of time to "multi-task."