an example of debugging with moldable tools
Locked
an example of debugging with moldable tools
 
|
Hi,
One thing we noticed over the past year since we introduced GT in Pharo is that people still tend to use these tools in a similar way classic tools were used. We think there is a more potential in these tools. To change this, we would like to collect stories of how using these tools enabled a workflow that was otherwise not possible. To get this started, we will start to document more consistently some of the sessions, and we would like to get input from your as well. The idea is to create a catalog of tutorials that people can follow and get inspired from. Let me start. I recently had to debug a small problem, and I ended up having an experience that I found beautiful: http://www.humane-assessment.com/blog/debugging-duplicated-behavior-with-gtinspector/ What do you think? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Don't give to get. Just give." _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Re: an example of debugging with moldable tools
|
|
On Wed, Feb 3, 2016 at 2:53 PM, Tudor Girba <[hidden email]> wrote:
> Hi, > > One thing we noticed over the past year since we introduced GT in Pharo is that people still tend to use these tools in a similar way classic tools were used. We think there is a more potential in these tools. > > To change this, we would like to collect stories of how using these tools enabled a workflow that was otherwise not possible. To get this started, we will start to document more consistently some of the sessions, and we would like to get input from your as well. The idea is to create a catalog of tutorials that people can follow and get inspired from. > > Let me start. I recently had to debug a small problem, and I ended up having an experience that I found beautiful: > http://www.humane-assessment.com/blog/debugging-duplicated-behavior-with-gtinspector/ > > What do you think? Great and enlightening work ! Actually, we spend more than one hour on this bug during last Pharo Sprint with Onil. We trace the problem to be linked to the duplication of Announcement creation somewhere, but we miss your knowledge ;-) -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
|
|
In reply to this post by Tudor Girba-2
On Wed, Feb 3, 2016 at 9:53 PM, Tudor Girba <[hidden email]> wrote:
> Hi, > > One thing we noticed over the past year since we introduced GT in Pharo is that people still tend to use these tools in a similar way classic tools were used. We think there is a more potential in these tools. When all your life you've only ever had a hammer and carry it on you tool belt, someone gives you a shine new toolbox full of every tool you are not familiar with, when you see a screw you forget to even look in the toolbox and by habit reach for the hammer. > To change this, we would like to collect stories of how using these tools enabled a workflow that was otherwise not possible. To get this started, we will start to document more consistently some of the sessions, and we would like to get input from your as well. The idea is to create a catalog of tutorials that people can follow and get inspired from. > > Let me start. I recently had to debug a small problem, and I ended up having an experience that I found beautiful: > http://www.humane-assessment.com/blog/debugging-duplicated-behavior-with-gtinspector/ > > What do you think? Very cool. Thanks for sharing. I think you have the advantage of intimate knowledge of the tools. (I hadn't known of "ContextStackSignal log".) But even my knowing a bit of Mondrian/Roassal, it was a lot to take in. For outsiders it might be a bit dry with the code samples foreign to them. But I think it would make a compelling video for outsiders. It is great to see it used in real life context, but for me to better adopt and utilise such tools, I really need hands on practice, and in another month that might not be a example to work through. Maybe it also needs some simple contrived tutorial, where you create . cheers -ben _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
Re: an example of debugging with moldable tools
|
|
Hi,
> On Feb 3, 2016, at 3:37 PM, Ben Coman <[hidden email]> wrote: > > On Wed, Feb 3, 2016 at 9:53 PM, Tudor Girba <[hidden email]> wrote: >> Hi, >> >> One thing we noticed over the past year since we introduced GT in Pharo is that people still tend to use these tools in a similar way classic tools were used. We think there is a more potential in these tools. > > When all your life you've only ever had a hammer and carry it on you > tool belt, someone gives you a shine new toolbox full of every tool > you are not familiar with, when you see a screw you forget to even > look in the toolbox and by habit reach for the hammer. > >> To change this, we would like to collect stories of how using these tools enabled a workflow that was otherwise not possible. To get this started, we will start to document more consistently some of the sessions, and we would like to get input from your as well. The idea is to create a catalog of tutorials that people can follow and get inspired from. >> >> Let me start. I recently had to debug a small problem, and I ended up having an experience that I found beautiful: >> http://www.humane-assessment.com/blog/debugging-duplicated-behavior-with-gtinspector/ >> >> What do you think? > > Very cool. Thanks for sharing. I think you have the advantage of > intimate knowledge of the tools. (I hadn't known of > "ContextStackSignal log”.) Of course. The goal of this exercise is not to brag, but to offer starting points for others. > But even my knowing a bit of > Mondrian/Roassal, it was a lot to take in. For outsiders it might be > a bit dry with the code samples foreign to them. But I think it would > make a compelling video for outsiders. > > It is great to see it used in real life context, but for me to better > adopt and utilise such tools, I really need hands on practice, and in > another month that might not be a example to work through. Maybe it > also needs some simple contrived tutorial, where you create . Indeed. That is why we are thinking that these examples should be accompanied by images in which people will be able to practice. I already preserved the current image. I will get back on this. Cheers, Doru > cheers -ben > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com "Every thing has its own flow." _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
|
|
On Thu, Feb 4, 2016 at 3:39 PM, Tudor Girba <[hidden email]> wrote:
> Hi, > >> On Feb 3, 2016, at 3:37 PM, Ben Coman <[hidden email]> wrote: >> >> On Wed, Feb 3, 2016 at 9:53 PM, Tudor Girba <[hidden email]> wrote: >>> Hi, >>> >>> One thing we noticed over the past year since we introduced GT in Pharo is that people still tend to use these tools in a similar way classic tools were used. We think there is a more potential in these tools. >> >> When all your life you've only ever had a hammer and carry it on you >> tool belt, someone gives you a shine new toolbox full of every tool >> you are not familiar with, when you see a screw you forget to even >> look in the toolbox and by habit reach for the hammer. >> >>> To change this, we would like to collect stories of how using these tools enabled a workflow that was otherwise not possible. To get this started, we will start to document more consistently some of the sessions, and we would like to get input from your as well. The idea is to create a catalog of tutorials that people can follow and get inspired from. >>> >>> Let me start. I recently had to debug a small problem, and I ended up having an experience that I found beautiful: >>> http://www.humane-assessment.com/blog/debugging-duplicated-behavior-with-gtinspector/ >>> >>> What do you think? >> >> Very cool. Thanks for sharing. I think you have the advantage of >> intimate knowledge of the tools. (I hadn't known of >> "ContextStackSignal log”.) > > Of course. The goal of this exercise is not to brag, Sorry, thats not what I meant :) which was that even though its well written, it threads together a few tools I haven't used a lot, so its hard to retain. Its has sparked my interest, but for it to soak in I need some hands-on practice. > but to offer starting points for others. > > >> But even my knowing a bit of >> Mondrian/Roassal, it was a lot to take in. For outsiders it might be >> a bit dry with the code samples foreign to them. But I think it would >> make a compelling video for outsiders. >> >> It is great to see it used in real life context, but for me to better >> adopt and utilise such tools, I really need hands on practice, and in >> another month that might not be a example to work through. Maybe it >> also needs some simple contrived tutorial, where you create . > > Indeed. That is why we are thinking that these examples should be accompanied by images in which people will be able to practice. I already preserved the current image. I will get back on this. I look forward to it. cheers -ben _______________________________________________ Moose-dev mailing list [hidden email] https://www.list.inf.unibe.ch/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |