I maintain the strategies summarized by Stuart are a better alternative than repetitive debugging sessions because they change the core of how you are thinking about design and coding, forcing you to have a broader view about how you are doing things and preventing problems before they appear.
I came to the same conclusion as Stuart after 30+ years of coding in various languages/assemblers and architectures. Debugger have been in use for more than 35 years and they never improved code quality. They were used to patch specific narrow problems, not avoiding them at the root. I had a colleague once that was writing code in hex directly in the debugger. Nice and exotic but of little value considering that he had to reconstruct source code afterward... and that he'd better not get his mainframe session disconnected while patching his code. I did not say that a debugger was not useful at all, I said that the importance of having a debugger is *overestimated* especially in an immutable world. Relying on a debugger as an important tool to support coding is like admitting the failure of your code before it runs. It's like conceding defeat before the fight has started. Trying to a avoid debug sessions as much as possible is more productive. Time spent in debug sessions is not spent on more important issues. Luc P. > > May I suggest that as useful as your strategies are, they cannot replace a > debugger? Let's be clear about our logic before claiming "it is not much > needed". Maybe YOU really don't need it, but that is different from > claiming it is not needed. > > A debugger as good as it is cannot replace the 4 first strategies. > > > > Luc P. > > > > > > > you to > -- > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Softaddicts<lprefonta...@softaddicts.ca> sent by ibisMail from my ipad! -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
