tpetrina

There is a lot of content out for vibe coding, but it mostly comes from solo devs. Are there teams who are vibe coding and how do they solve the general problem of trust. Sure, vibing for myself is fine as I will suffer the negative consequences - but would you send PRs for code review if you haven't really worked on the code? I like vibe coding for small solo stuff, but I am looking for experiences from people where multiple devs vibe code on the same codebase. My gut feeling is that it cannot really work when multiple people are involved. And, to be completely honest, I would neither feel good sending this code to someone nor I would like to review something vibe coded by someone else.

Let's say you have people higher on the corporate ladder on a technical level whose opinions you do not respect. This can be because they are either fluffy talkers, ivory tower architects, devs promoted beyond their skill level, people with no experience in the current project, and more.

Simply put: you don't trust their experience in general and you don't trust that their input for this project is relevant. On top of it, it is fluffy and boils down to "make better code". As if anyone consciously wants to make bad code.

If they are setting the stage for technical decisions, but you simply do not trust them, is this something that can be improved upon? Or you just switch companies. How to "disagree and commit" in that case? How to appeal to their managers or someone else? What if the manager above sees no issue with such people?

As applications become more complex they start requiring proper FAQ, documentation and more. How would you approach it from the tech/writing side? How to keep screenshots up to date? What about ease of editing/publishing/translating? How should articles be linked from the app itself? I have a feeling that web never got that built in ? Button Win32 apps used to have.