I guess this would be my first post regarding my profession in this blog. I’m not going to discuss actual technology, but rather an issue which keeps coming back and will always recur.
An experienced programmer, much like novice ones - is always introduced with new technologies and is required to learn to use them, sometimes in ways that completely override what he used to know and how he used to do things. Sure, there are those who after getting their degree or finished a course started a job somewhere in the 80-s and have since not shifted to new platforms and languages. Most of us though, do program for Windows - and Microsoft has created many new and exciting things every year or two.
Being a developer mainly on windows machines, I’m always in need of upgrading my knowledge of the latest technologies. As I browse through the latest MSDN magazine discussing what’s coming soon in C#4 a thought came to me: Should one approach studying the “very next technology” as an extension to what he knows – or as if he is a completely new developer first encountering the technology? Go through the “books for dummies” and “learn xyz in 10 days” books, or perhaps just go through some documentation of “what’s new” and just flip through some samples?
Simply continuing with what’s already known and adding a few new things here and there could miss on the simplicity offered with new technology. One may get stuck in the “old way” of doing things. This gives new-comers a certain advantage of using the new tools in the way they were intended and actually creating less clutter in his workflow.
It seems to me like a good exercise to try out at times: Approach the next upgrade of technologies as a novice, rather than an experienced programmer – and see how the creators of new technologies intended it to be learned and used.
Thinking out loud.
Cheers!




-->