> Frans Boumw:
>
> > Well, one idea could be to drop E&C requiring
> coding styles.
> > It's that simple. E&C propagates sloppy coding 'because you
> can fix it
> > during debugging anyway', forgetting that debugging is
> costly and time
> > consuming and should be avoided until the only way to
> determine what
> > causes a bug is to start the debugger, carefully placing
> breakpoints
> > etc.
>
> That's ignoring the discovery and prototyping potential of E&C.
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.
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
