Mon 17 May 2004
Category : Technology/paymentsNews.txt
Here's another interesting site that made a reference to ours : Scott Loftesness, and from which I've found Payments News, a survey of developments in the field of electronic payments. It's so interesting to find something just when you need it. I've been wondering why we couldn't just use PayPal to accept normal credit card payments, instead of having to sign up with WorldPay or Planet Payment or stuff like that.
I've learnt from this PayPal page that this is now possible to receive credit card payments from people who may not want to create a PayPal account (that wasn't possible before).
And I've learnt from this link on Payments News that there are further interesting developments at PayPal.
I've often wondered what's the point of doing all this writing. This is probably the answer, that I get to learn at the same time. That's the reward for taking part.
Category : Technology/UsableHelp.txt
I like to look up the web server log files to see how our site is being used and what information people are looking for. Occasionally, I find some very interesting sites that have made references to ours, and here is one :
Usable Help - "Examining documentation and help systems for software and consumer products." I think it's a very useful site for developers, with very interesting ideas. Definitely worth a visit.
Business @ the Speed of Stupid
Category : Technology/bizatspeedofstupid.txt
I picked this book up from the Special Offers bin yesterday and have been reading it since.
Business at the Speed of Light? More like, Business @ the Speed of Stupid - "a comedy and a tragedy in every chapter", according to an Amazon.com review. This ought to be required reading for users, business owners, and IT practitioners alike because "the business landscape is littered with the remains of thousands of technology ventures", and we need to get everybody to understand why this had happened and how we can do better.
While reading the book, I've been thinking about the comment I made in the last post about taking just eight weeks to bring a client-server-based application onto the web. If it gives a feeling of bravado, of the sort that comes out quite foolishly on the pages of "Business @ the Speed of Light", then I must hasten to add that a lot of trial and mostly errors had preceded it, through a couple of projects I did on the side, using other failed approaches.
I had learned, from the failures, to value the whole body of code that had already worked. And that the key to getting things done is controlling complexity, and not let the tail wag the dog.
So the point I was trying to make was that, when IT departments insist on issues like standardisation on the languages and platforms they had "blessed", above all other considerations, they may be underestimating the dangers they're exposing their business. They may look like they're simplifying things, but actually creating a combinatorial explosion of complexity. They like to say things like, "the web server must be .Net, or whatever, compliant, or we won't endorse it", and my stomach turns the way it's been described for many of the unfortunate souls who populate the "Business @ the Speed of Stupid" book.
Finding a way to get along with IT departments, managing the expectations of users, and living with the limited project management skills of the IT coordinators in-between - these are the hardest challenges facing external IT developers and consultants.