eriksmartt.com/blog

  • arduino (3)
  • art (2)
  • austin (39)
  • automotive (15)
  • blogging (25)
  • books (10)
  • business (3)
  • code (15)
  • design (10)
  • diy (3)
  • django (8)
  • experience (17)
  • family (2)
  • film (4)
  • food (1)
  • for:optaros (2)
  • gadgets (11)
  • games (11)
  • garden (3)
  • green (5)
  • hack (13)
  • hardware (11)
  • hci (9)
  • life (13)
  • lifehack (11)
  • links (70)
  • linux (8)
  • living (3)
  • make (3)
  • media (7)
  • mobile (98)
  • music (2)
  • news (17)
  • osx (29)
  • outdoors (4)
  • privacy (2)
  • product-management (1)
  • python (74)
  • quote (3)
  • security (10)
  • society (20)
  • software (38)
  • spam (2)
  • syndication (5)
  • technical (30)
  • technolust (5)
  • transportation (12)
  • travel (25)
  • ubuntu (7)
  • web (66)

  • Search:
     

     

    How to become a genius

    “You must clarify your goals, gain knowledge through spaced repetition, preserve health, work steadily, minimize stress, refuse interruption, and never resist sleep when tired. This should lead to radically improved intelligence and creativity. The only cost: turning your back on every convention of social life.”

    Citation from: Want to Remember Everything You’ll Ever Learn? Surrender to This Algorithm.


    Post Comment »


    Any shape or size…

    “when an object can be any shape or size, what shape or size should it be?”

    I love following Jan Chipchase’s Future Perfect blog. It documents an amazing level of ethnographic research that most companies simply don’t have the luxury to participate in. The quote above is a closing slide in one of his presentations. It stuck me because of it’s dual use as both a design meditation, and a serious question designers of any product should be able to answer. It also begs the reverse question for existing design:

    If this object could have been any shape or size, why did it end up like this?

    (Via: Insight & Innovation: Design Research, Nokia Connection 2007 [ppt])


    Post Comment »


    Ninety-ninety rule

    “The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time.”

    Ninety-ninety rule


    2 Comments »


     

    A few books I'm reading now:

    A few books I'd recommend: