Michael Hurley

I ve been working on permission and role management for a B2B AI product.

One thing that makes this tricky is that a user s role doesn t always tell you what they should be able to do.

For example, someone might manage a project without managing the entire workspace. They need control over their project s settings and members, but that doesn t necessarily mean they should have access to organization-wide settings.

This creates an interesting UX problem.

One thing I find tricky about vibe coding as a product designer is keeping changes focused.

Let s say I want to adjust a specific interaction or improve one part of a screen.

AI might make the requested change, but also modify the layout, spacing, or components around it.

The result isn t necessarily worse. Sometimes it even looks better.

One thing I keep noticing with vibe coding is that small UI changes can sometimes take more prompting than expected.

You ask AI to adjust the spacing. It changes something else. You explain it again. The result gets closer, but now another detail is off.

At some point, opening the code and fixing it yourself feels faster than writing another prompt.

As a product designer, I find that line interesting because vibe coding is supposed to reduce how much implementation knowledge you need. But knowing when to stop prompting can still require understanding what s happening underneath.