If I’ve done this right, this post will appear on my Blogger Blog and my Vox Blog, and my LJ…
PUSH THE BUTTON!
Day: May 20, 2008
Eric lifted his head up out of his hands. They were wet from the tears that were still silently streaming down his face. His eyes were red, raw from him trying to rub them dry and banish this outward display of grief, even though there was no one there to see it.
He looked across at the bed. The nurses had disconnected the drip and ventilator, pushed back the machines and dimmed the lights a little. He could tell that they wanted to extubate as well, but that would not happen until the post. Despite all of their efforts Jenny did not look at peace; she barely looked like herself.
Eric made himself really look at her. A voice in the back of his mind kept telling him that he would only have so many more chances to commit her face to memory, even this injured version of her face. He had expected to see her face every day for many more years to come. If he had known he would have paid more attention to it, learned it more closely. Now he would have only a few photographs to help him keep her in his memory.
—
You can see the original post on Ficlets.com by clicking here.
One of the things I like more than anything about my job – I am a coder by profession – is that there is always room for improvement in any application. There is no such thing as a ‘perfect’ app and there is always something that can be improved upon if there is the spare time to do it.
I am currently contracting at a company called Pitch, working on a project to deploy several websites, or versions of a single web-application that delivers a web-site, across a bunch of territories. While we wait for other bits of the business to send us translations and configuration details that are territory-specific, we are taking the opportunity to tighten up the codebase and ‘do things better’. If you’re not a coder then I should explain that this process is often referred to ‘in the biz’ as re-factoring.
Why is this so satisfying you ask? Well it serves two good purposes, in terms of providing satisfaction. The first is that it reminds us (coders) that there is nothing wrong with accepting that applications are generally better if they evolve than simply coming into being, and secondly that as imperfect beings this means we need to create, use / test and __then__ refine in order to get the best results. Embracing this not only means that we will get better results in the end, but it will also take just enough of the pressure off to allow us to remember why we started coding in the first place; solving problems is first and foremost a FUN way to make your living…
This morning my train into Paddington was quite badly delayed; this is not unusual…
Anyway, just outside the station as we were waiting for the platform clearance the train manager came onto the tannoy to apologise, which he did and then during his patter he said:
“…I’m afraid to say that the only good news I can give you is that on the 1706h and 1806h you can now use cheap day returns and off-peak travelcards, which is a measure that came in yesterday…”
and the thing I never thought I’d hear was the carriage breaking out into spontaneous laughter; irate commuters and day trippers just seeing the funny side together. It was remarkably nice.