On a related note, with the recent release of Pharo 8, someone said[1]: > I'm sure the author of this language uses the IDE like many people feel when they play minecraft. It's a playground of ideas for those who really love OOP.
[1] https://www.reddit.com/r/programming/comments/erd65s/pharo_80_the_immersive_pure_object_oriented/ff3cgl6/ For me, live coding has been part of bringing back this playful feeling to programming. Something difficult to experiment with the indirection of editing files approach of most computing programs and environments, except for the Jupyter alike interactive notebooks, but the difference is the moldability, uniformity and simplicity of Pharo live coding experience over other interactive notebooks languages. Cheers, Offray On 18/01/20 7:07 a. m., Edward K. Ream wrote: > The recent Aha's re the connection between unit testing and coverage > testing have turned computer programming into an utterly absorbing > adventure. Computer programming now feels like playing a video game! > > The analogy is exact! > > In a video game, you have more or less clearly defined goals. (In some > games the goal is to figure out what the goal is.) To attain those > goals, there is a well defined set of actions you must take. In > well-crafted games, those actions are pleasurable in themselves, or at > least not utterly tedious. There are also a set of obstacles, which > make attaining the goals non-trivial. There is also usually a score > that measures progress. All these combine to make a computer game it's > own little universe. > > Likewise with computer programming. You have more or less clearly > defined goals. There are also actions, obstacles, and now, with > coverage testing, a score. Programming is now it's own /structured/ > universe. The goal gets translated to unit tests, which all must pass > with 100% coverage. > > *Summary* > > Unit tests translate a possibly ill-defined goal into something > concrete, specific and well defined. The task is, by definition, > complete when all unit tests pass with complete coverage. > > Coverage testing allows uncovered code to be discarded when all > relevant tests pass. This was a completely unexpected, and most > welcome, development. > > The entwined tasks of creating unit tests and ensuring complete > coverage almost completely structures the task of programming. As a > result, programming is /more/ engaging and compelling than ever before. > > Folks, this is a big deal. > > Edward > -- > You received this message because you are subscribed to the Google > Groups "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/28875ae4-d8b6-46fe-8b30-13557bf8eaae%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/28875ae4-d8b6-46fe-8b30-13557bf8eaae%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/2c25e969-7755-b55a-fcaf-2800b02a0099%40riseup.net.
