IMG_4373.jpeg:oar

Revision 5243
In a noisy pub

Probably not the best place to test a new core component, but hey - I’m busy during the day, and only this website will be effected.

So far, so good. Just one minor variable warning, and no obvious problems with the page layout.

Ok, so now I’m finding a few glitches, but still nothing serious, which is pretty good considering I ripped a big chunk out of the middle of this thing. I tend to do that when I find myself looping through code not quite sure if things are all in the right place.

Thwack the hacks

My code continuously, gradually evolves. I’ll be making a change to one system and have an idea about making something more client-editable, or I’ll simply see an opportunity to consolidate code - to write one function to replace ten.

To introduce new code without breaking older stuff sometimes involves some nasty ‘if this is the place for this hack’ hacks, and developing a lot of new ideas rapidly or developing paradigm shifting changes can lead to a situation where it feels more efficient to simply wipe the board and rebuild. It’s not for the faint of heart though. It usually means that you can’t check out your code until you’ve rebuilt the thing you’ve destroyed, and that probably will take longer than you think. What am I saying? If you’re a techy everything takes longer than you think.

And then relax

For all the pressure that a ‘delete and rebuild’ operation puts you under, the result is knowing how everything works, where everything is, and that everything is required. An ephemeral, ethereal nirvana that just needs something…