I want to refer to a question that was asked at the NAVTechdays 2011 and about that I also thought in the last few month. It was the first question in Christian Abeln session and I think Christian didn't give a proper answer to this question. I mean from a certain point of view this is the only answer someone from Microsoft could give. But there's also some truth in what you could read between the lines of this question.
In general the question was about: What kind of methodology does Microsoft (or someone else) provide to qualify traditional NAV developers so they get used to the new possibilities of .NET? An NAV developer should know something about databases, table relations, business logic and so on, a .NET developer lives in a complete different world. That maybe will cause some problems in future. I'm sure this will not happen in every situation, because there are some specialists that are able to live in both worlds. But there is a certain risk if you hire an NAV developer that your solution doesn't consider all possibilities of new technology and on the other hand if you hire a .NET developer that not all NAV database issues are covered.
From my point of view this question also implies the following: What will be the future of NAV developers? You know SQL becomes a bigger topic in future, web services as well, form and report design is going to change, maybe cloud computing and network could be an issue,... I think maybe it's possible that we won't have a single NAV developer but several for different parts of NAV. And that leads me to another question: From a companies point of view, how should someone decide which way to go with his traditional NAV developers? I mean NAV is not a development tool, it's an ERP system with some possibilities in development. So, you need someone who knows about the business logic, not so much about the programming language (that's easy to learn for someone who's able to program). That means, should you qualify your current developers in terms of .NET or should you hire .NET developers and teach them how to understand and implement business logic?
You see, I have some doubts about the right way and there're plenty of open questions about the future. So, I want to hear what you guys think about that...
"Money is likewise the greatest chance and the greatest scourge of mankind."