Code as a Rhythm

Changes don't happen overnight. Or at least, that's not the end of it.

Working on big invasive changes in production code poses it's own challenges. But after going through the motions over a couple of major releases I'm learning that even though the actual workload underhand maybe breaking new terrain in my personal corner of the world, whether it'd be learning about C, imap, mime or warping my head around threads and event-driven designs - the kind of work, effort or mental labour if you will, continues to be much the same all along.

It's not just about 'sticking with it' - though persistency does help alot. It's also about feeling the rhythm, and respecting it. Just don't rush it, keep the pace, feel the beat, if you know what I mean.

There are bigger cycles, with smaller ones within. Changes are steps, bound in a pattern all of their own. From a prototype 'proof of concenpt' change, to 'pattern established: implement' change, to a consistency change wrapping it up. Consistency changes demonstrate and finalize one of those cycles. They clean-up and codify a new element of elegance, beauty if you will. It's when the code underhand starts to smell right again, and any bugs are easily tracked down and fixed with minimal effort. Until of course, the downhill ride ends where the next hill rises to the horizon...

Trackbacks

    No Trackbacks

Comments

Display comments as (Linear | Threaded)

    No comments


Add Comment


Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA