[TriPython] A question of recursion and nested parsing

[Ken MacKenzie]

I need to sit down and watch that.  Probably need to make some of my
coworkers do the same.  I try to be very liberal with criticism but I also
like to see proof that the criticism holds weight and of course the
criticism is better with an alternative solution.  However I am a person
that believes the best code comes from 10 versions that preceded it that
proved to be the wrong way.  The reason is a scientists, failure IS a
result and it is an important result, if not the most important result.
Nothing scares me more than when my code compiles/runs without obvious
issue the first time.  That is usually a sure sign that something really
bad has happened.

It is kind of like what I say about the game of chess...  You learn more
when you lose than when you win.

On Fri, Sep 15, 2017 at 3:04 PM, Calloway, Chris <cbc at unc.edu> wrote:

> On 9/15/17, 2:35 PM, "TriZPUG on behalf of Ken MacKenzie"
> <trizpug-bounces+cbc=unc.edu at python.org on behalf of ken at mack-z.com>
> wrote:
> > I feel that if one is not ready for criticism of their code then
> > they should not put it out publicly.  I mean that is the point of open
> > source anyway.
>
> Very much in the spirit of Stacy’s featured talk last month:
>
> Slides: https://geekgirlbeta.wordpress.com/2017/08/14/code-
> reviews-using-art-critique-principles-the-slides/
> Video: https://www.youtube.com/watch?v=xpqwuaCW6os
>
> The flipside is that we should be cognizant of the fact that human beings
> are receiving the criticisms we make and so offer them in a way that is not
> personal. David Handy is a shining example of such good behavior.
>
> These two sides are reflective of a very old programming maxim: “Be
> liberal in what you accept, and conservative in what you offer.”
>
> --
> Sincerely,
>
> Chris Calloway
> Applications Analyst
> University of North Carolina
> Renaissance Computing Institute
> (919) 599-3530
>
>
-------------- next part --------------
   I need to sit down and watch that.** Probably need to make some of my
   coworkers do the same.** I try to be very liberal with criticism but I
   also like to see proof that the criticism holds weight and of course the
   criticism is better with an alternative solution.** However I am a person
   that believes the best code comes from 10 versions that preceded it that
   proved to be the wrong way.** The reason is a scientists, failure IS a
   result and it is an important result, if not the most important result.**
   Nothing scares me more than when my code compiles/runs without obvious
   issue the first time.** That is usually a sure sign that something really
   bad has happened.

   It is kind of like what I say about the game of chess...** You learn more
   when you lose than when you win.
   On Fri, Sep 15, 2017 at 3:04 PM, Calloway, Chris <[1]cbc at unc.edu> wrote:

     On 9/15/17, 2:35 PM, "TriZPUG on behalf of Ken MacKenzie"
     <trizpug-bounces+cbc=[2]unc.edu at python.org on behalf of
     [3]ken at mack-z.com> wrote:
     > I feel that if one is not ready for criticism of their code then
     > they should not put it out publicly.** I mean that is the point of
     open
     > source anyway.

     Very much in the spirit of Stacy***s featured talk last month:

     Slides:
     [4]https://geekgirlbeta.wordpress.com/2017/08/14/code-reviews-using-art-critique-principles-the-slides/
     Video: [5]https://www.youtube.com/watch?v=xpqwuaCW6os

     The flipside is that we should be cognizant of the fact that human
     beings are receiving the criticisms we make and so offer them in a way
     that is not personal. David Handy is a shining example of such good
     behavior.

     These two sides are reflective of a very old programming maxim: ***Be
     liberal in what you accept, and conservative in what you offer.***
     --
     Sincerely,

     Chris Calloway
     Applications Analyst
     University of North Carolina
     Renaissance Computing Institute
     [6](919) 599-3530

References

   Visible links
   1. mailto:cbc at unc.edu
   2. mailto:unc.edu at python.org
   3. mailto:ken at mack-z.com
   4. https://geekgirlbeta.wordpress.com/2017/08/14/code-reviews-using-art-critique-principles-the-slides/
   5. https://www.youtube.com/watch?v=xpqwuaCW6os
   6. file:///tmp/tel:%28919%29%20599-3530