Currently Reading Refactoring: Improving the Design of Existing Code By Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts see related

Dad was very perceptive with that last post. Little did he know that Nathaniel's favorite cord is the USB printer cable. Anyway, more drivers, more instability.

Kind of a weird experience today. Came home, and Windows had crashed and rebooted itself today. I logged on and there was this weird window up that I had never seen before. The flashiest virus ever. Turns out that it is some piece of software by ASUS and is poorly translated and appears to have no actual purpose. Anyway, uninstalled the ASUS utilities and it went away.

I hate to call the code I'm working with at work spaghetti code, because I would hate to insult spaghetti code everywhere. This is more like you took the spaghetti, put it in a blender for 5 seconds, and then put is back. It is horrible. My boss started it. He is a mechanical engineer with some programming experience. Then, the guy who took it over from his did most of it and did some refactoring. His code is better, but still leaves a LOT to be desired. As near as I can tell, it spawns a child thread that does all of the work while the parent thread exits, because someone copied an example they didn't take the time to fully understand. So, I got a book on refactoring today. It is 9 years old, but, from what I saw, it is still THE book on the topic. So, in computer terms it is practically an antique.

Nathaniel just had his first bite of banana. He really liked it. He had no problem trying to get more of it off of mommy's fingers. He even tried to gnaw on it, and probably would have succedded at getting off a chokable piece if Steffanie had let him.