|
|
|
|
|
|
by enraged_camel
23 days ago
|
|
|
>> I'm seeing this applied to every role across organizations. The designer that gets heard is the one who can vibe code the best. Same with strategists, writers (seriously), and other people for whom "coding" is not remotely their expertise or function. It's not about vibe coding the best, it's about delivering value the fastest. And the value in this case is bringing clarity to the conversation when there are a lot of unknowns. As the article notes, prototypes are great for that. It's much easier to poke and prod at a prototype and use it to explore the problem space than to sit in on a presentation where the slides are just heavily distilled versions of an engineering design doc that is dozens of pages long (and most people will just skim anyway). |
|
|