@Frank: you are absolutely right, but it's difficult to generalize this, as it highly depends on your situation.
I have seen hello-world kind of code that was very easy to understand, but also very complex, but very clean code to meet a lot of financial (security) requirement, or code with many visitor patterns to be able to handle different kind of products (subclasses). In these latter cases, it can cost you a lot of time to understand, even when it's very clean and good coding....... Often analyzing the code cost more then making the change... (according to statistics: solving bug consists 70% of code/issue analyzing). On 10 December 2015 at 18:01, Frank <frank.wyna...@gmail.com> wrote: > If you have to read code for hours to solve a problem without a debugger I > think you have some bigger problems with your code than some bugs... (code > structure) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "GWT Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit/IfLWnnCf9rM/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > google-web-toolkit+unsubscr...@googlegroups.com. > To post to this group, send email to google-web-toolkit@googlegroups.com. > Visit this group at http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
