Why crashing your car on purpose is a smart thing to do… Sometimes.
Posted in Cars, Models & Gadgets on 18. Dec, 2009 | 0 Comments
Many people I know will tell me I’m being irresponsible for doing this myself, let alone telling others to do it. However, I saw one of those people nearly trash £55,000 worth of Porsche by simply letting go of the wheel and hitting the brakes when the back end broke loose, so what the hell do they know?
When you’re dealing with a car that’s losing control, you need to know how the car behaves in order to concentrate on getting it back in check. When you start losing control, you have seconds to react and fix it before you go past the point of no return. If you’re already compensating for your car’s tendency to pull right under heavy braking in the snow by the time it happens and putting in exactly the right amount of steering in to stabilise the car and allow stability control to do its job, you have a much better chance of coming out of it without a dented car or skull than someone who’s thinking “Shit, what’s what crunching sound?! Why is my car pulling to the left? Why has my car lost power?”

Normally, I write a “Postmortem” 
My favourite kind of programming is framework programming. Designing a component outside of the complexities of a whole application allows you to design beautiful, clean APIs and components. In fact, every single application I write or am a part of writing ends up shipping in components. Music Rescue for Windows, for instance, has a library for talking to iPods which I wrote, a library containing user interface controls which I wrote and the application (which my colleague wrote) imports them both and assembles it all together into an application.