On Jan 31, 2014, at 2:19 PM, Pharo4Stef <[email protected]> wrote: > I love the changes of Johan. I would love to have a more compact class > definition :) > Now the question by henrik is really puzzling me.
But is not working, isn’t it? I mean for the people. I don’t want to be critical here, only to analyse this case of decision process because on the heat of the trenches this things are easy to miss... Imagination is not market fit. Before deciding to break tradition, shouldn’t validation come first? If so, our method to make decisions risks to be overexposed to audience misfits. Misfitting the statu quo is okay, misfiting your audience one too many times is a formula to end up alone (AKA having a product nobody wants to use). Lets say you have an idea to innovate on UI or the API... you can go ahead and prototype how it feels for yourself even a partially implemented draft of the idea (lets say a branch). Lets says it convinces you… Time to be skeptic. Test. Test with someone else. Tests it with 5 guys and ask how they feel about it. Hear. So to yourself the hard and useful questions: Do they validate? signals of market fit? are they strong? convincing? are they weak? so are they worth now? are you sure they are being honest and not saying yes just to be nice, to please you? When you don’t validate you’re doing software for yourself in front of others. That’s cool until is not. What are Pharo's usage metrics these days? sebastian o/
