Stream
Streams is officially the best thing I’ve made for the internet. Pity it’s only limited to Telegram users though.
How do you balance “algorithms to accommodate asynchrony, not always-on engagement” with the fact that the best interactions happen in real-time?
The really hard bits of productivity (planning, intensity control, quitting) get way too little attention relative to how important they are. The default is to just sloppily drag yourself forward.
Found these absolutely perfect box-shadows from Jen’s lab.
box-shadow: 0px 1px 3px rgba(0, 0, 0, 0.4);
Almost two years after writing my first JavaScript function, I’ve finally learnt to use HTML form elements.
In other news, WOFFER is now live.
nvm it’s down because replit messed up.
Well, the Streams beta is done. That’s one project down, 5 to go.
An underrated fact of picking a good design system is that working within (and around) it just feels so right. You no longer have to second-guess the structure of new components and can let most decisions be made by the fundamental system.
This is what work-in-progress looks like.
Think I should just accept that I want to ship a bunch of code right now, and get it over with. Six projects in a month will be intense, but doable.
Working on a new site design for Shreeda, and thinking about what goes into a personal website. High-level categories seem to be:
- things I am
- things I do
- things I like
Setting up my stream…
It’s nice to have markdown working in here, as well as HTML elements. Grateful for unsafe mode.
Funny how I seriously considered a captain’s log layout as the design for this section.