Jeremy retweeted
Replying to @cansar @RoamResearch
While there are benefits to a standard reading interface, you lose lots of the character and cues of a web *site*. Web pages are more than just content - they‘re designed locations that you *visit*. There’s value in digesting them in context, imo.
Jeremy retweeted
Replying to @rroudt
This is one of the key strengths of nocode in my view: the ability to distribute workload across your tech/“non-technical” team. Introduces a gradient to the scale of traditionally technical jobs to be done.
Jeremy retweeted
Replying to @cortexfutura @RoamResearch
I do “progressive structuring” - only layer structure as needed, when and where the lack of it is an impediment. Reduces overload and ensures each addition has a clear why. @RoamResearch is great for this. Works with team processes too.
Jeremy retweeted
"It is hard to be the best at something unless you enjoy doing it." stanford.io/1qkX7Da #entrepreneurship
Jeremy retweeted
The first step to becoming a good product manager is accepting that you add no value a priori and that everyone is aware of that.
Jeremy retweeted
Beautiful project. When pictures tell a story: help find the locations of Grandpa’s photos to restore his memories. grandpas-photos.com/
Jeremy retweeted
Useful Sketch and Swift resources: designcode.io/learn
Jeremy retweeted
Web wins for reach.
Native wins for engagement.
Each is great for something different.












