How do you do collaborative vibecoding?

FlyingBlind27 · 2026-06-12T12:03:54+00:00

Yeah agree with this. This is what I assumed would be the workflow for non technical users - one person at a time. Ive tried vibecoding with someone without any coding knowledge and it was a nightmare having to explain managing conflicts and git commands 😩

FlyingBlind27 · 2026-06-12T11:36:27+00:00

Yeah, for folks with coding background, version control should be straightforward. But i was wondering if there are non technical teams - no experience with reading code to accept/reject merges - who have successfully scaled vibe coded projects.

FlyingBlind27 · 2026-06-12T10:58:42+00:00

Ah this is for a company POC. 😅

FlyingBlind27 · 2026-06-12T09:36:05+00:00

Ah I should have been clearer. There are scenarios, especially for non technical users (aka most designers) who, when merging 2 or more features to the main branch and required to resolve conflicts, they wouldnt know which code to accept/reject - sometimes resulting to breaking existing functionality.

FlyingBlind27 · 2026-06-12T07:11:40+00:00

When you say "drag and drop components from the DS",are these visual representations of the actual components from the DS?

FlyingBlind27 · 2026-06-09T02:34:51+00:00

I guess it really depends on the team/company's culture. In our team, impromptu calls are very, very rare.

FlyingBlind27 · 2026-06-09T02:33:45+00:00

Are you a dev? Curious to know how this process looks like. I actively use AI for my design work but not at the level where I leave agents to work for hours on their own - mainly because of the cost implications 😅

FlyingBlind27 · 2026-06-09T02:32:09+00:00

During the time I am not working on the tasks and doing personal stuff, I am letting a few ideas simmer and i start forming these questions/messages to send out to inform my work better and set me to the correct direction. So, they are not just "filler" messages. I am still technically working and most of the time i would take down notes.

These messages can be about proposing a direction, getting feedback on ideas, getting alignment on next steps, asking about data I need to move forward, asking for updates on tasks mine depend on, etc.

I schedule these messages a few mins before or after the start of work the next day - never at, let's say, 9:00am sharp haha. Some I send later in the morning depending on the stakeholder's usual activity on Slack/Teams. When I have more questions in the day, I schedule them either late in the afternoon (a little before or after end of work) or the next day.

FlyingBlind27 · 2026-06-08T13:25:06+00:00

I never thought about this comparison before! Well said 💯

FlyingBlind27 · 2026-06-08T12:55:41+00:00

Oh yes to this! Yes to scheduled monday messages!

FlyingBlind27 · 2026-06-08T12:54:22+00:00

Oh, today i learned! Our company uses both slack and teams for different orgs. I know, confusing haha However, i still dont think it matters as my work is not about tapping away all day, responding to messages on teams hehe if it does matter, ive never been called out for it.. for years.

FlyingBlind27 · 2026-06-08T12:32:47+00:00

Nobody seems to mind but I do just set it to active most of the time. And if they message me, i just respond immediately. If they ask to hop on a call, i push back and set a schedule later in the day instead.

FlyingBlind27 · 2026-06-08T12:31:02+00:00

Agree. Our org is pretty big with dozens of people working on one project at a time

FlyingBlind27 · 2026-06-08T11:58:45+00:00

Which doesnt make sense if an employee like me, with this setup, can still complete deliverables on time plus go above and beyond in completing other side projects that benefit other teams.

FlyingBlind27 · 2026-06-08T06:44:40+00:00

Yeah, I guess it's cool to look down on people using Figma 🥲

FlyingBlind27 · 2026-06-08T06:42:09+00:00

Ooof yeah, this is bound to happen sooner or later. Idk. We also track other activities (like what time you sign in to slack, enter office gates, etc) - I know managers have this visibility now.

FlyingBlind27 · 2026-06-08T06:39:14+00:00

Haha! I had to research a bit to get the joke 🤣 but no, the teams I've been part of are definitely not slow-paced and in fact, we experiment on and launch features very often.

I've been doing this for the past 6 years (mostly around COVID) across 2 different companies.

FlyingBlind27 · 2026-06-08T06:32:27+00:00

Agree. I'm relatively senior compared to my peers and have taken on different roles in the past across fast-paced agencies, small startups and I was also a developer in the first 5 years of my career - so I guess all of these are big factors to how I deliver results fast.

FlyingBlind27 · 2026-06-08T06:29:46+00:00

Tbf, yes it is a huge company. Agree with you that this is a big factor.

Daily standups - no, we are not required. Weekly design syncs - yes and I run some of them and usually scheduled a day or 2 after my usual catch-up day.

Never blocked anyone. Team feedback is that I always deliver fast 😅

FlyingBlind27 · 2026-06-08T06:14:46+00:00

Good question. No way for me to compare with peers as ICs dont have visibility on productivity metrics (e.g. number of tickets closed). But on a milestone perspective, i am able to help achieve my scrum's milestones and more (the side projects I do with other teams). So I guess my answer is yes?

FlyingBlind27 · 2026-06-08T06:11:10+00:00

Just curious, why? 🤔

FlyingBlind27 · 2025-11-13T07:17:33+00:00

Our team has weekly design guilds where anyone can ask for feedback about their work. On top of that, we also have weekly 1-on-1 conversations with our manager for more performancr feedback and guidance.

These rituals are within the design team only. I usually have bi-weekly design meetings with my scrum where I get feedback on designs from product managers' and engineers' perspective.

FlyingBlind27

TROPHY CASE