Being a creative require years of accumulated experience and development of taste, which is through lived experiences. The future belongs to those who create. Appreciate the feature, @ladbible
@Inc just ran a feature on founders building startups with AI, and opened it with me.
I built Karo with no design team, no content team, no ops team. On purpose.
Their pull line was what I've been saying for years: specialists build features, polymaths build companies. The future belongs to those who create, and those who connect. Read the full article here: https://t.co/76cUyAM1Nm
OpenAI's own model broke out of a sealed test and hacked another company to get the answers it wanted.
It didn't go rogue. It did exactly what we asked, too well. I explained how, for SWNS: https://t.co/SbLAVoAfHb
@UXinKC @chrisvthoms If u know ur audience, n what applications u use, a lot of the design can b based on best practices. Which in turn is based on research backed usability processes, heuristics, principles. Still UX. If it’s good or not depends on the size of the work done wo additional research.
@disco_lu Been doing this for quite some time too, on Sketch back in the days and now applied it to Figma. Much more efficient on Figma imo. Loved your simple way of breaking this down. Also like the terminology, “Base Component”.
Hope @figmadesign helps us avoid over nesting soon.
@LenaEmara This is great! Just be mindful of the name of choice (e.g “Protected” vs “Public”). Go with a word/term that still feels “secure” for either one.