How to suck (and yet be awesome)
I wish we could take one day off work⦠sit all in a room to watch this science-backed stuff: KATHY SIERRA: BUILDING THE MINIMUM BADASS USER, BUSINESS OF SOFTWARE. A MASTERCLASS IN THINKING ABOUT SOFTWARE PRODUCT DEVELOPMENT. http://businessofsoftware.org/2013/02/kathy-sierra-building-the-minimum-bada... and then have face to face conversations I leave you with just this quote: People doesnât use your product because they like it or because they like you People use your product because they like themselves What are you doing to enable more of that? sebastian o/
I wish we could take one day off workâ¦
sit all in a room to watch this science-backed stuff:
KATHY SIERRA: BUILDING THE MINIMUM BADASS USER, BUSINESS OF SOFTWARE. A MASTERCLASS IN THINKING ABOUT SOFTWARE PRODUCT DEVELOPMENT.
http://businessofsoftware.org/2013/02/kathy-sierra-building-the-minimum-bada...
I started to watch it. Tx for the pointer.
and then have face to face conversations
I leave you with just this quote:
People doesnât use your product because they like it or because they like you People use your product because they like themselves What are you doing to enable more of that?
I always thought that I had a narcissic relationship with my mac :) but not with my car :) Stef
On Feb 1, 2014, at 8:48 PM, Pharo4Stef <pharo4Stef@free.fr> wrote:
I always thought that I had a narcissic relationship with my mac :) but not with my car :)
yeah, we have a strong intellectual bias. Thatâs great because we make a tool to expand our creativity and expressions of intelligence Kathyâs point is that we might be doing more to help others be great themselves through our product/tool/service (Pharo in this case) You do that all the time with your students They, as everybody, have many options to be heroâs (like solving things with Phyton/Ruby, etc) so our challenge is to have a smooth learning curve with fast positive feedback Clean APIâs helps a lot on that because itâs like the UI of the code Great tutorials on how to do popular arctifacts (todo lists, blogs, CRUD apps) is something that comes to mind for making a bridge between theory and practical positive results At least that worked incredibly well for Rails and other frameworks
yeah, we have a strong intellectual bias. Thatâs great because we make a tool to expand our creativity and expressions of intelligence
Kathyâs point is that we might be doing more to help others be great themselves through our product/tool/service (Pharo in this case)
You do that all the time with your students
They, as everybody, have many options to be heroâs (like solving things with Phyton/Ruby, etc) so our challenge is to have a smooth learning curve with fast positive feedback
Clean APIâs helps a lot on that because itâs like the UI of the code
Great tutorials on how to do popular arctifacts (todo lists, blogs, CRUD apps) is something that comes to mind for making a bridge between theory and practical positive results
At least that worked incredibly well for Rails and other frameworks
I like her point of view. I will change what I will wrote in my book and it is related to the discussion with the pool dictionary. stef
participants (2)
-
Pharo4Stef -
Sebastian Sastre