product designers are the architects of software.

architects create blueprints, instructions for others to hit hammer to nail.

what if architects could create blueprints for cranes, instead?

in other words, why are you, a product designer, using figma instead of vibe coding?

because any sufficiently complex solution  still needs a human engineer in the loop, and those designers are working on such solutions with those engineers rather than with just LLMs. 

same reason I often work with a designer and not just loveable or equivalent. 

I broadly don't think narratives like "X specialist really has the most power now with AI" are that good, because you can feasibly replace X with anyone: exec, PM, UI/UX, designer, dev, etc and get the same take.

mostly reading and building. 
prev: @clankfun, improbable, github, amazon. https://ntik.me

I get that but modern society has forced many people to have a multifaceted skillset 

fewer and fewer people get to be experts in one thing and be successful

agree people need to have a multifaceted skillset now more than ever

I mean you can still be a deep expert at the very edge of one thing and succeed (e.g. nuclear physicist) but we're mostly talking about building consumer apps and saas here where there are 5-6 distinct skills that used to be split across cofounders but now don't need to be

agree people need to have a multifaceted skillset now more than ever 

https://farcaster.xyz/garrett/0x2b07d218

better now to become a generalist and get an intuition for every part of the process that used to require a highly differentiated expert, and stop thinking of yourself as a product designer/dev/exec/whatever