144/365, originally uploaded by craigand.
Mini-digger with a freaky effect. This is basically a hand-held shot with some serious camera shake. The interesting swirls are caused by the lens's image stabilisation completely failing to help.
Part of the minidiggers set.
139/365, originally uploaded by craigand.
A plant grows in a disused cupola outside the Kelham Island development in Sheffield. The circular border is provided by one of the many small holes clearly visible on the other side.
I also took this picture of the outside lip of the cupola. I couldn't decide which to use, but I figured the plant one was unlike anything else I've taken. Here is the other contender.
132/365, originally uploaded by craigand.
Was feeling uninspired today, so I used the @dailyshoot for inspiration. The brief was to make photograph dominated by red. Well, I saw this Triumph TR 250 in the car park, and I saw that it was red. So there we go.
I also shot this lovely black and white pic. The B&W, combined with the swirly bokeh of my 28mm Makinon lens, make it appear almost anachronistic.
129/365, originally uploaded by craigand. A rather damp, surprisingly empty Meadowhall carpark turned a little reflective after the downpour.The second post set in a car park in 3 days. Can you tell what I've been doing a lot of lately? Yep. Shopping in the rain.
Just kidding. I'm not going to rail against coding standards. No, I'm going to rail against the absolute and dictatorial enforcement of coding style guidelines, to the point where a single misplaced curly bracket can fail the code review of a thousand line project before it's even started. I'm going to rail against the fact that many people these days don't actually know that coding style guidelines and coding standards are not the same thing.
Coding style guidelines are not coding standards. Coding standards are rules on how to construct software. Rules that have practical and defined benefits. Rules than can be proven to assist in the structured and correct building of code. For example: Do not perform database access in the constructor.All database access should use the framework's DAL.Do not rely on complex instantiation instructions; provide a factory method.Do not inherit from a class in a different module or library; only encapsulate.Avoid singletons.Don&…
Canon EOS500N, originally uploaded by craigand.
New toy. Well, the body is, anyway. Already had the 28-135mm stuck on the front of it. EOS 500N to complement the EOS 500D for if I fancy using film once in a while. Only cost £7.99 including postage, so ... bargain!
This is, of course, why there are a few grainy, filmy looking pics of late. Unfortunately half the "new" film I had turned out to have already been exposed. It just wasn't wound back in to the canister. Hope to get some more exciting pics over the summer using lower ISO film and a film scanner (well, borrow my dad's ...) rather than just scanning 6x4 prints.