Hi kevin,

>"Thinking that you need real programming experience in .NET to do this IMO is a myth and a sign of narrow mindedness."


>Thats like telling people your an expert on a certain type of car while having never
>had drivin it yourself, just because you researched it.

Which is totally valid when a F1 car designers from Ferrari says he is an expert on F1 cars since he worked and researched F1 cars at different teams, but never drove such car and was depended on the feedback from the drivers.

It might be hard to swallow, but the people with the most insights into these kind of issues, don't actually do much practise.

Again, C.J. date and E.F. code did not build (m)any (?) database applications. Their knowledge comes from making abstract models of product characteristics and what that means in database design. In the real world a developer often is too much focused on implementation to be able to think a lot of the bigger picture. That's the role of an application designer, which gets its feed from a system/information analyst.

Walter,