Have you ever made a coding choice that later you can not rationalize?
All the time, until I started using version control and reviewing my choices on a weekly , even daily basis ( refactoring ).
Its like when you first start writing code, you end up with 10-20 line if-blocks, 3-5-8 indentation levels deep, and it feels very comfortable because its all very fresh in your mind.
It's not until you're forced to revisit that code a year later that you realize how difficult it is to read, and start turning each long if-block (or indentation level ) into a function (refactoring).
schwern has a slideshow about this skimmable code where he tackles refactoring WWW::Mechanize
There is also a shorter version of the skimmable code talk, in the longer version he subliminally introduces Method::Signatures
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||