fatVerified account

The more I occupy this space the more I’m convinced that the only way to effectively support it is by reimagining orgs through a post-structuralist lens. Until then there’s always going to be this weird tension in the work being done and the degree to which collaboration happens.

This is why mark and I worked so well together when we were creating bootstrap. Mark is an engineer-y designer and I’m a design-y engineer. But even then, twitter’s organization didn’t really know how to support a team like that, so it all happened outside of work in free time.

For me, this is why “design system” teams and the work they put out often struggle. What’s actually required are team members operating in-between two dominant modes / two cultures. The most effective design systems come at the intersection of these roles, when the roles blur.

Oh? You’re an engineer? here’s your engineering ladder, here’s your engineering org. You’re a designer? here’s your design ladder, here’s your design org.

For how progressive/futurist tech claims to be it’s always funny to me how outmoded titles (and org structures) still are.

build a castle in sand, watch everyone pour water on it

$2999 per month (for a year lease), $3250 for 6 months (lease takeover) - dms opennn (or if you want more pictures / video - or just to say hey :P)

maybe this is why designers homes are always so much nicer than engineers homes - need that fig tree to create a safe space

design review culture is kinda amazing… imagine if once a week all the engineers on your team logged on and group reviewed your pr live