Hacker News new | past | comments | ask | show | jobs | submit login

I have used a similar technique for teaching competitive croquet. Instead of this one simple rule, I offered three. The first two rules pertain to strict technique and croquet theory (similar to the specifics about not leaving pieces hanging, and structuring your opening moves). The third rule is always: don't F up your shot.

In the chess example, I reconfigured the 'don't do stupid shit', to something like, a) Open with an intent, b) Don't lose pieces without purpose, and c) Do everything for a purpose. I wanted to add this information to the thread, because I think the 'don't F up your shot' croquet analog includes a more explicit sense of limiting your actions based on your ability. In croquet, all the theory and mental prowess in the world is sacrificed if you can't execute the ideal shot under the circumstances. This is acknowledgement of your current ability is what I think applies to much of programming (and life).

Note that I am NOT suggesting that you avoid moving your abilities forward. However, focus a lot of effort on knowing what you know, and learn how to use it well. The more you use it, the more you learn and expand on that skill set. The more carefully you use what is within the realms of that skill set, the fewer mistakes (and the more successes) you will have.




> "a) Open with an intent, b) Don't lose pieces without purpose, and c) Do everything for a purpose."

I use similar rules when investing, playing poker, and in competitive video games. I'd phrase them as:

- begin with a goal in mind

- take deliberate actions (that you are capable of) that advance you toward your goal

- don't give up resources (money, chips, pieces, hitpoints, etc.) unless that advances you toward your goal




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: