Monday, 11/16/2020

09:28 life lessons adam smith

thinking vs going with the flow


  1. structured approach

  2. go with flow

    no higher-order thinking
  3. improve structured thinking

  4. improve go with the flow

  5. evaluation

  6. specific models

    src knowing a name for something doesn't mean you know anything about the thing. names are so arbitrary if the path to victory is not clear, do nothing train harder than you fight sometimes reactionary responses can be too strong and need a middle way fast:alone, far:together keep your identity strong be good to yourself and others or neither



perseverance and passion for long-term goals. entails working towards challenges and maintaining effort for years dispite failure, adversity and plateaus in progress.

grit is different from self control: self-control is a local decision made on the day to day, while grit is made over the course of months, years of lifetimes. committment to a vocation does not derive from hourly temptations. grit is the best predictor of success - iq doesn't scale, and local self-control doesn't generalize to a global effort. willpower is probably limited; if it is, using willpower for one thing will diminish it for other things. grit can also be substantially diminished when everyone works super fast and gets early traction, then gets tired of chasing their goals and runs out of energy focus on what you want to be gritty about!

always add polish

src difference between success and failure if experiences don't have a polished and seamless user experience, they will fail. how do you quantify polish? we all need this emotional polish! adding polish lowers the emotional energy needed to interact with and respond to emails, interfaces, etc. engineers fail at this and fail easily, but it's so so important.

20:02 privacy tools

we can never be private enough, but we can take measures to mitigate the actions of others
lots of great privacy resources
host your own federated server
forum to discuss self hosting

20:14 malleable software

The tragedy of modern computing: too often we conform to the software, rather than molding it to our needs. How can we empower everyone to edit their tools? Here are 3 ideas I think can help us get there. programming is the stone age! the user should still be able to see their objects and act on them in familiar ways browser extensions as semantic wrappers wrap apis in simple interfaces to help users create interactions with the webpage!

local-first software

this has probably been linked many times. it's about getting yor data out of cloud services and silos.

empowering users to customize chrome extensions via in-browser databases designing and programming malleable software end user customization by direct manipulation inspirations for work on this software oh my god