Check out this Dust mite inspecting some nano gears. Awesome.

Courtesy Sandia National Laboratories, SUMMiTTM Technologies, www.mems.sandia.gov

Many programmers go through a gradual occupational awakening. When I wrote my first small programs, I thought, “Once I get the program to compile and quit getting all these syntax errors, I’ll have computer programming figured out.” After I stopped having problems with syntax errors, sometimes my programs still didn’t work, and the remaining problems seemed even harder to figure out than the syntax errors. I adopted a new belief, “Once I get the program debugged, I’ll have computer programming figured out.” That belief held true until I started creating larger programs and began having problems because the various pieces I implemented didn’t work together the way I thought they would. I came to rest on a new belief, “Once I figure out how to design effectively, I’ll finally have software development figured out.” I created some beautiful designs, but some of them had to be changed because the requirements kept changing. At that point, I thought, “Once I figure out how to get good requirements, I’ll finally have software development figured out.” Somewhere along the path to learning how to get good requirements I began to realize that I might never get software development figured out. That realization was my first real step toward software engineering enlightenment.

from Orphan’s Preferred

I have to admit that this is spot on for how my education in Programming has gone to this point. I also have to reccommend the article as it does a neat job of comparing programmers to pony express riders of the past.