Monday, January 14, 2019

It's Going to Be what It's Going to Be

Last week, I had a vision of how I was going to design the networking part of the game I'm writing. This morning, I was all set to execute on that vision.

As I was reviewing the code, before the change, I discovered some things that needed to change. So, instead of doing what I planned, I did what was right. I cleaned up the code.

In the course of my cleanup, I uncovered a better design for the networking part of the game.

There's an important lesson, here. The forces acting on your code are going to be what they are going to be. So let the code be what the forces want it to be.

It probably won't cost you anything and, every once in a while, it grants you an insight of incalculable value.

Literally.

The value of a little discovery like that cannot be calculated because you can't tell how much its absence would have cost you.

Experience, however, allows me to estimate the cost as "a lot".