Frans: > Heh, sorry, but are you suggesting that writing code in a debugger > (which I think you meant), is 'OK' ? Because I don't > think it is. But that can be because I'm in the think first, do later > camp, while there are a lot of software developers who think > that doing and thinking can be combined during hammering in statements.
When I started developing in C# I very quickly lost all the bad E&C habits I had grown used to in VB6. To this day I still write code to avoid that requirement. However, I spend quite some time, more often than not on Saturday afternoons, experimenting and discovering platform and language features. This is not "writing code in a debugger", but what I called "discovery". What happens if I do this? What happens if I change this value? This would be very slow if I didn't use E&C for this purpose. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
