Tuesday, January 10, 2012 2:38 PM
As an architect, I stress to my team, colleagues or anyone that wants to talk IT that a solid developer needs to understand the fundamentals of how things work – especially when dealing with such a large framework such as the .Net Framework.
I’m usually very slow when it comes to adopting new versions of the framework, as of now I still write code in 2.0/3.5 while 4.5 is about to start collecting dust. It has become clear to me in the past years that sometimes frameworks simply get bloated. I wrote comfortable powerful and sophisticated applications with .NET 2.0 but when 4.0 came out everyone claimed it and jumped, yeah - I started writing code in assembly, therefore, I believe in less layers which is what newer framework versions are usually made up of.
If a framework does not provide with critical patches and newer features, then there is no need for me to upgrade. simply converting 6 lines of code to 2 lines by wrapping it is just not enough.