> Douglas Crockford says in Peter Seibel‘s excellent Coders At Work: The place where I found that to be most effective was taking testing, sort of, to the ultimate: going to visit customers. I did some of that early in my career and that was a great experience, having to go live with a customer for a week, helping them to install a new system, and helping them to work out the problems with using it. It gave me a…
>A post in two parts. First of all – thanks to Magus on #django for pointing out one of my errors to me. I’ve been working through Practical Django Projects over the last couple of days and it talks about having named urls. Take a look at these three one liners: # from urls.links.py (r’^$’, ‘archive_index’,link_info_dict, ‘coltrane_link_archive_index’), # from urls.py (r’^weblog/links/’, include(‘coltrane.urls.links’)),# In my template I get the url using {% url coltrane_link_archive_index %} We give our view a name…
>With apologies to The Monkeys I thought unit tests were just for fairy talesNever had the time to do things rightGoing live was frantic Development a drag Changing all my code got real bad Then I wrote my tests, now I’m a believerWithout a trace of doubt in my mind I’m in love – mmmmmmm I’m a believer, best thing I’ve ever tried Ahem. Or something. I’ve just made substantial changes to two of our production systems over the last…