The Tower of Hanoi Shows the Challenge of Being a Good Programmer

Have you ever heard of the tower of hanoi?

I first heard about the tower of hanoi, reading the text “Concrete Mathematics” before I had any business doing so.

Navigating a combinatorial ocean ravaged with dialectical forces is the true challenge of programming, whether it is addressing societies’ broken programs and promises, by resolving political conflict, or making a drawing app that tries to bridge the connection and manage the tension between small scales and large scales in our perception.

One reason why large programs take much more effort than small scripts, is because one is a pond, the other is a lake, and then there are other “systems” run by “programs” which are literally oceans and worlds.

We often judge difficulty by the size of one dimension, instead of considering the perimeter or the volume of the space penetrated by the structural computational byproducts we create called programs.

The tower of hanoi is an engaging story about priests who perform the development of history until the end of the world. It is a game that explores how the sequential progression of deterministic processes can create a rich and engaging narrative, when our knowledge is limited, of an underlying process which is completely determined and sequential, we would call it boring.

I can’t say what I ultimately think about the ideas the tower of hanoi suggests. Are we just priests performing history, in a linear process involving serpentine patterns?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.