I just finished reading this article that, I think, I got from Mike. It is freaking hilarious. He goes on for pages about technological addictions. Things that “how did we ever live without”, even though they didn’t exist last year. The other item he spends a long time on is how those devices set patterns in our live. One particular peeve that I share is Power Point, “Start putting what you want to communicate in PowerPoint slides, and everything you want to say is ordered into half a dozen bullet items.” And finally he gets to the meat of the article, which is, intellisense rots your mind. Probably only useful for programmers, but:
For example, for many years programmers have debated whether it’s best to code in a top-down manner, where you basically start with the overall structure of the program and then eventually code the more detailed routines at the bottom; or, alternatively, the bottom-up approach, where you start with the low-level functions and then proceed upwards. Some languages, such as classical Pascal, basically impose a bottom-up approach, but other languages do not. Well, the debate is now over. In order to get IntelliSense to work correctly, bottom-up programming is best.
Powerful stuff there. It has trained me, and I haven’t even considered that I was doing that. I can’t even imagine going the other way again. Ugh. Methinks I need to go back to LISP for a while.
Those patterns get set up in your life. They aren’t necessarily bad, but it is nice to at least see them happening, and deciding that you want to be conditioned in that manner. I like the way my cell phone has conditioned me. I don’t like the idea of my IDE conditioning me to think about how to solve problems. I leave you with another gem…
Everyone agrees that one of the most important elements of writing self-documenting code is giving your variables and objects meaningful names. If Visual Studio really wanted you to write good code, every time you dragged a control onto your form, an annoying dialog would pop up saying “Type in a meaningful name for this control.” But Visual Studio is not interested in having you write good code. It wants you to write code fast.
and one more, on programming C in notepad with gnu C, “It’s just me and the code, and for awhile, I feel like a real programmer again.”