I got admonished at my new job for coding practices that have become second nature to me. Is aggressive refactoring really that scary?

My co-worker tests his code with the toString() and visual grep method. I’m not sure he would have ever caught the bug on his own. I keep trying to explain that unit tests are a Good Thing…

Several years ago, I worked for a small software shop. The company had gone through its number of growing pains, but seemed to be well established by the time I joined. Time would prove me wrong, and also give me some things to remember if ever I start my own small business.

I’ve noticed lately that the number one search term that brings people to this site is “flicker vertigo”, sometimes combined with “aspartame”. It seems time to revisit this problem.

I picked up the June/July issue of Scientific American Mind soleley for the article on the Science of Burnout. I was feeling particularly frustrated with work at the time and it was nice to read an article telling me that things I had been feeling were not out of the oridinary.

Okay. I’ve had the MacBook for a couple of weeks now, and I think I may finally be getting the hang of it. I did have to break down and purchase an actual computer manual - something I don’t think I’ve ever done. But, the results are worth it and I can now answer the questions I asked in my previous post.

In my Valleyschwag post, I complained that I just needed a MacBook to affix all of my stickery goodness to. Thanks to a good price on some employee stock options and the permission of my wife, I’m writing this on a brand spanking new MacBook.

For some time now I’ve suffered from Computer Vision Syndrome (CVS). Most computer users have CVS to some degree or another - it’s pretty common. I also seem to have a susceptibility to flicker vertigo as well. Strangely enough, I’ve been unable to find very much material that talks about flicker vertigo in terms of computer use in an office environment.