Development Blues

Things have been a bit quiet here of late, mainly because I’m snowed in work time with one big project that’s dealing with a metric fuckload of data coming in by XML. It’s aq nightmare in many ways – and also decidedly scary because of the sheer amount of personal data involved in each record.

Additionally, the company that we’re connecting with are – to be polite – not all that helpful. I got to see their documentation before we started the project, and that looked OK. However, the documented examples don’t actually match up in any useful recognisable form with what we’re getting out of the process.

During this week, among other things, the company has realised that the documentation they sent us initially was out of date – two versions out of date, no less. So they said they’d send the latest/greatest version. And then sent the self-same two-versions-out-of-date documents. The file actually has the version number on it, so it’s not (or at least you wouldn’t have thought it was) rocket science in the least to be able to send the correct documentation.

Once we’d got the up-to-date documentation, I queried the data coming back from the company, as it didn’t match the examples given. Oh yes, I was told, “We can’t put in examples for everything.“. Yes, you can – particularly when it’s what your customers are using to develop their interactions with.  Random data format changes aren’t helpful either – “We’ve stopped sending the numbers with four decimal places – yes, we know our documentation says we do this, but we don’t any more

As you can imagine, it’s making life pretty difficult. There’s a lot to do still, and I can’t rely on the information from the original company. Always a joy.



Leave a Reply

Your email address will not be published. Required fields are marked *