Using Infinite Loops to Stalemate Kids

 INFINITY! - Imgflip

You know how kids start asking "WHY?" to everything to try to annoy their parents?
Pro-tip: Find a series of answers that loop and just keep repeating them until the kid gets annoyed.
...
Why?
So the tree can grow.
Why?
So they can get bigger.
Why?
So they can get more sun.
Why?
So they can get bigger.
Why?
So they can get more sun.
etc...

The kids get bored and give up.

Comments

Post a Comment

Popular posts from this blog

Engineering Truisms

This is a brief collection of quotes, laws, and truisms that I've gathered over the years.  I've kept those that have consistently proved themselves across organizations and projects during my career.
Read more

The Importance of Pace

Image
  In The Simpson's episode Homer's Enemy ,  Frank Grimes is a unlucky man who's worked hard his life but failed to reap any of the benefit.  When confronted with the inequity of his circumstances compared to Homer's he breaks down into a self destructive fit of jealousy that eventually ends his life prematurely.   The episode is a 1990s comedic expression of the general observation that life is not fair.  Several decades later, as income inequality has increased it's become a popular talking point that, "Hard work alone doesn't make you successful."  In Gen A slang a, "Try Hard" is someone like Frank Grimes who does himself discredit by giving it too much effort. For us conscientious types, this is not only counter intuitive but also elicits an emotional reaction.  Folk heroes like Rocky show us that while God may not have blessed us with any particularly useful talent, we can make up for it for it with heart.  Hercules taught us that even wi...
Read more

The Telescoping Constructor (Anti-Pattern)

Image
The Telescoping Constructor Looks like this: Widget(varA) {...} Widget(varA, varB) {...} Widget(varA, varB, varC) {...} or Widget widget = new Widget(x); widget.setVarA(...) widget.setVarB(...) widget.setVarC(...) There are both shared and specific problems for each variety.  Let's talk about both. The 1st case, supernumerary constructors. What's wrong with this? Well, the good news is you provide  quiet consumption since there's a bespoke constructor for every use case.  Rather than have noisy construction, where the consumer must fill in a bunch of nulls, you move the noise into the implementation.  We shouldn't make assumptions on how many times the class will be used, so keeping the complexity to ourselves is generous and will lead to a more maintainable macro system. However, one problem here is that the end consumer is not restricted in their choice of constructors.  Like shopping at the super ...
Read more