Yesterday we saw how easy it is to send text messages using the SDK, so now let’s try making a phone call.
Category: Software
As I mentioned recently, I now work in the Web21C SDK team. The SDK provides a simple API for programmatically accessing various web services that BT provides, including SMS, conference calls and location services.
The SDK is in public beta, and is currently free (with daily usage limits). Up to now it’s only been available for those crazy .NET folks, but the next release (on Monday, all being well) will extend that to Java, PHP and Python. Rumour has it that Ruby’s in the works too.
I’ve been having a play with the Java version – here’s a sneak preview…
A recent article in the New York Times describes the issues of introducing ‘The Toyota Way’ to non-Japanese factories.
Categories
The other kind of SOA (reprise)
Jason Kolb has an insightful post today on the same kind of issue that I was talking about in the other kind of SOA.
Categories
Fighting Developer Abuse
This ThoughtWorks recruitment ad is pure genius.
I was having a discussion last night about the value of learning new programming languages. I said I still felt I ought to learn Lisp, even if I was never likely to use it in anger, because it would hopefully give me a new way of thinking about problems which would be transferrable to other languages (especially ones like Ruby). Alkesh (come on, get a blog so I can link to it!) felt that Lisp was a dead language, and would be no more useful than learning Fortran or COBOL.
Then this morning I tried the Which Programming Lanuguage Are You? (via Steve Freeman).
Fate?
Most large organisations have been using SOA for years, and they’ve been doing it despite their IT strategy, not because of it. No, not Service-Oriented Architecture, but Spreadsheet-Oriented Architecture.
Simon Baker has posted a response to John Scumniotales’s post on Team Leadership and Self Organization, and I have to say I’m with Simon.
AS I mentioned at the end of this post, I’ve been convinced by Dan North’s case for using the “given when then” pattern for specifying scenarios during behaviour- or test-driven development, and while I wait for JBehave to be released, I’ve been playing around trying to come up with a way of using the pattern to clarify intent in (Java) unit/acceptance tests.