Throwback to [[June 24th 2016]] - playing with @TheTedNelson's zzStruct demo
Would be incredible to navigate twitter threads like this
A few days later - trying to design a visual interface for a youtube filter that could express -- Videos about chemistry, favorited by accounts I follow, created by a user who is followed by 3 friends....
and you think my design was bad in 2018 :)
Two years later, starting to look almost like @RoamResearch
How @RoamResearch solves the problems that Google hasn't - ironically, my oldest recorded pitch is probably only thing out that talks about our long term vision.
Not touched in the video - how the layer on top of the web we're building is end-user programmable, an environment for @worrydream style Explorable explanations, and written in #clojure
If you think you should work at Roam, email support@roamresearch.com with your pitch on why we should hire you now. We might not get back to you for a while, and if we do @MikejNorman might be pissed that we didn't have job spec written for the role first, but shoot your shoot.
This is the deepest injustice no one talks about, and one we have a chance to actually do something about with software... without the system’s permission.
Law is the code of our social operating system, we can build better tools for understanding it, using it, and changing it.
Here's 30 min of me live coding for block level styles - what I'm doing here is possible for literally anyone with a roam account - or with edit access to a roam graph
Most of the productivity discourse seems to be about top-down planning
Most how we think and talk about project management is in that paradigm too
My focus is on bottom up project management:
Breaking things down into ever smaller pieces - then exploring how they fit together
I find that when folks try to organize big projects in @RoamResearch their first instinct is to try to use kanban boards and lots of pages to approach things in this top down way
The real connective tissue of big projects is the block reference though.