Smalltalk › Pharo › Pharo Smalltalk Developers

the importance of your story

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Tudor Girba-2

the importance of your story

Hi,

I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse.

There are several things I would like to emphasize.

I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art.

One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer.

But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you.

While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago.

Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo.

Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from.

Cheers,

Doru

www.tudorgirba.com

"Every thing has its own flow"

Tudor Girba-2

Re: the importance of your story

And here is the video:

https://vimeo.com/131632605

On Thu, Jun 25, 2015 at 1:39 PM, Tudor Girba <[hidden email]> wrote:

Hi,

I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse.

There are several things I would like to emphasize.

I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art.

One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer.

But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you.

While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago.

Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo.

Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from.

Cheers,
Doru

--
www.tudorgirba.com

"Every thing has its own flow"

www.tudorgirba.com

"Every thing has its own flow"

Max Leske

Re: the importance of your story

In reply to this post by Tudor Girba-2

Thanks Doru!

On 25 Jun 2015, at 13:39, Tudor Girba <[hidden email]> wrote:

Hi,

I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse.

There are several things I would like to emphasize.

I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art.

One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer.

But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you.

While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago.

Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo.

Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from.

Cheers,
Doru

--
www.tudorgirba.com

"Every thing has its own flow"

philippeback

Re: the importance of your story

Yes, thx.

Your words are inspiring.

At a time I needed that lift :-)

Phil
Le 25 juin 2015 13:54, "Max Leske" <[hidden email]> a écrit :
>
> Thanks Doru!
>
>> On 25 Jun 2015, at 13:39, Tudor Girba <[hidden email]> wrote:
>>
>> Hi,
>>
>> I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse.
>>
>> There are several things I would like to emphasize.
>>
>> I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art.
>>
>> One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer.
>>
>> But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you.
>>
>> While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago.
>>
>> Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo.
>>
>> Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from.
>>
>> Cheers,
>> Doru
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing has its own flow"
>
>

abergel

Re: [Pharo-users] the importance of your story

In reply to this post by Tudor Girba-2

Thanks Doru for your inspiring words.

Recently I had a “coup de blues” because Pharo is completely absent from the StackOverflow and Github scene. I feel it is like a researcher without a webpage. Without a webpage, he does not exist.

But I have faith things will soon change...

Cheers,

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Jun 25, 2015, at 8:39 AM, Tudor Girba <[hidden email]> wrote:

Hi,

I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse.

There are several things I would like to emphasize.

I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art.

One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer.

But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you.

While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago.

Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo.

Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from.

Cheers,
Doru

--
www.tudorgirba.com

"Every thing has its own flow"

Max Leske

Re: [Pharo-users] the importance of your story

On 25 Jun 2015, at 15:56, Alexandre Bergel <[hidden email]> wrote:

Thanks Doru for your inspiring words.

Recently I had a “coup de blues” because Pharo is completely absent from the StackOverflow and Github scene.

It might not have “much traffic” on SO but the number of posts per week has grown *significantly*. A lot of the questions seem to com from GSoC students of CS students from around the world which is pretty cool actually.

I feel it is like a researcher without a webpage. Without a webpage, he does not exist.

And here I thought researchers defined themselves through the number of publications :)

But I have faith things will soon change...

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Jun 25, 2015, at 8:39 AM, Tudor Girba <[hidden email]> wrote:

Hi,

I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse.

There are several things I would like to emphasize.

I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art.

One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer.

But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you.

While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago.

Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo.

Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from.

Cheers,
Doru

--
www.tudorgirba.com

"Every thing has its own flow"

SergeStinckwich

Re: [Pharo-users] the importance of your story

In reply to this post by abergel

On Thu, Jun 25, 2015 at 3:56 PM, Alexandre Bergel
<[hidden email]> wrote:
> Thanks Doru for your inspiring words.
>
> Recently I had a “coup de blues” because Pharo is completely absent from the
> StackOverflow and Github scene. I feel it is like a researcher without a
> webpage. Without a webpage, he does not exist.

I also have this "coup de blues" from time to time for similar reason
and because I have to fight sometimes to defend this choice.

Thank you Doru for giving us inspiration for the future.

I will come to ESUG this year. This is usually a good place to have a
boost for several months after.

--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

stepharo

Re: the importance of your story

In reply to this post by Max Leske

Yes doru this is reasoning in me and I should restart to work for real on Coral because we could change the face of scripting languages.

Le 25/6/15 13:53, Max Leske a écrit :

Thanks Doru!

On 25 Jun 2015, at 13:39, Tudor Girba <[hidden email]> wrote:

Hi,

I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse.

There are several things I would like to emphasize.

I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art.

One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer.

But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you.

While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago.

Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo.

Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from.

Cheers,

Doru

--

www.tudorgirba.com

"Every thing has its own flow"