


Product & process. Creator of Shape Up. Prev: 37signals. rjs@ryansinger.co


Project management should be 80% design, 10% logs, 10% tasks. The clearer the design is, the fewer tasks you need. Some logs are necessary for capturing why the design is the way it is.

Management is defining where we want to be and making trade-offs to get there.

Tasks are waste. Design decisions are what ship.

It's imperative vs declarative. I shouldn't be telling people "turn left, turn right." We should be agreeing "this is where we want to be" and everyone figures out how to navigate there.

Every project management tool tracks work to be done. By definition issues and tasks are instantly outdated as soon as an agent does them. What we need to track are the things that SHOULDN'T change! The design, the agreements, the boundaries. Tasks are just the diff to that.

Loved this talk by Kelly Spendlove on isolating dynamics into neighborhoods youtu.be/YC6hnhRRM_A?si=RH2q…

Seems @Shopify could be well-placed to hold your digital likeness for trying on clothes. Like how Shop Pay holds your payment details, your avatar is part of your identity and should move from store to store with you.

I held my nose on a few GraphQL projects and tried to understand the appeal. My conclusion is that it's a way to avoid making decisions. To avoid having to come to an agreement or commitment with others. Some engs really want that and willingly pay in complexity for it.
Everyone at this point agrees that GraphQL was a bad idea, right?

The creativity unlock is real. Amazed by the art and animation and data viz and more showing up in my feed every day.

So much creativity is coming to software.
My wife is making an app with Claude Code to scratch her own itch and her UI judgement is amazing. Claude offers a traditional design pattern for something and she'll go "no, I want it to be like this..." which is outside conventions and actually way better.

My wife is making an app with Claude Code to scratch her own itch and her UI judgement is amazing. Claude offers a traditional design pattern for something and she'll go "no, I want it to be like this..." which is outside conventions and actually way better.

The domain model is an interface to the extent it provides affordances (words, semantics, grammar) to express state and perform operations.

Personality is back
Since Apple Music and Spotify designs are so boring, I built an iPhone Duo app called Duoamp that is a throwback to Winamp Shake it and a new Winamp-style skin appears

Fantastically intuitive visualization
"the greatest whitepill of all is that local minima are rare in high dimensional spaces"