This is certainly my experience. I have had quite an eye opening experience upon this subject. In recent times I have written java and TSQL. In both situations a debugger was not availible. At first I floundered and flapped ever time I hit a problem. Soon my old skill started to return. I started writting tighter code, with suitable debugging tools built within it. I used program by contract to ensure validity of data entering and exiting methods, I wrote validation methods as part of my objects to be called in times of problems, I wrote extensive debugging output toggleable at runtime. Now I am back in perl land (for a time) I have my debugger back but find I use it less as my code is tighter.
Anything that does not kill your project makes you stronger
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||