If I survive that lot and the accompanying partying networking then I’ll be one happy girl. Wish me luck, and if you’re going – I’ll see you there :)
Last time I did this I refused to tag anyone but this time I’m going to take the opportunity to introduce some of my blog readers to blogs I read myself.
EmmaJane – we have the same middle name and she’s also a geeky knitter
Girls Can’t What – Gretchen has a site full of brilliant female role models, and she’s an ace designer
dotjay – he tagged me last time, and he should blog more
Erik – a cool colleague who will be surprised by this tag
urbanwide – I joke that Deb is “the other girl developer in Leeds”! She’s a camera geek, ruby developer, and she helps me understand how “girl” goes with “geek”
Cally – the then-girlfriend in question
Mark Aitken – ex-colleague, mentor and friend
And now the rules:
When I received and unpacked the book, it was a little lighter than I had expected, however REST really isn’t rocket science and can easily be covered in a tome this size. Overall it was well-written (with only as many spelling mistakes as any other PHP book) and clearly organised. The author begins by skating over why we don’t want to use SOAP, and shows his enthusiasm for REST as a replacement. However before the true elegance and concepts of REST are brought out and revered, we skip straight along and start to look at examples. Very few services that claim to be RESTful actually are, which makes writing anything along these lines very tricky, however I did feel the author could have been clearer about why having a single URL and a parameter for which action should be performed, doesn’t fit well. We do get a sense of excitement about services as ways to “glue together” bits of data on the net, and the possibilities of exposing and consuming information in this way.
Several frameworks are mentioned that can be used with REST, I’ve only heard of one (Zend Framework) – and this book works through a number of examples of working with Zend Framework to provide a REST service. The examples throughout are very thorough – starting with designing the service and getting the semantics of HTTP verbs sensibly applied. We are then taken through building the service using Zend Framework, creating a library class of functionality and then setting up the server to respond to incoming requests. For anyone using this book it is also worth checking for more up to date tutorials; Zend Framework has regular releases and some of the information in the book is already out of date – the dangers of the cutting edge!
On a personal level I’m not a big fan of frameworks; Zend Framework is a favourite but the use of it in this setting means that there is a large amount of the book dedicated to Zend Framework, the MVC pattern, and other things that aren’t really anything to do with REST. Call me old-fashioned but for me RESTful services need only HTTP and a data format of some kind, JSON or XML, and a good understanding of the grammar and structure of something that “smells” RESTful. In this book I got bogged down in the cookbook-style examples and lost sight of the bigger picture. The chapter summaries and best practice pointers though were great and I hope readers do take note of these.
If you need to build a RESTful service and you don’t mind Zend Framework, then this book will attempt to guide you through the process and explain plenty of useful stuff along the way. For a mid-level PHP programmer coming in to services for the first time, I consider this book a nice entry point. However if you were hoping to pick up the concepts behind RESTful services and look to apply them in your own work, then your $40 would be better spent on the RESTful Web Services from O’Reilly – you won’t be copying and pasting working PHP code, but you will come away with some great ideas.
On a personal level, I met up with lots of friends and also made several new ones – one of the best things about the conference for me was being able to meet “in real life” the friends I’ve made online, either on IRC or through my site or the phpwomen site. There were people there that I’ve met through my work and through attending other tech events – and to be able to shake hands and chat in person was great.
We also had a phpwomen stand at the event – which generated quite a bit of interest. For the record, we counted around 15 women in the 174 attendees, which is actually quite a lot – or rather, its more than usual – and it was great to see it. Also there were 2 female speakers out of 16 which was accidental but is also quite a good ratio so I’ll mention it (hi Steph, hi Zoe!)
All in all, it was a pretty stunning first conference – I’d like to personally thank Jeremy and the people from his family and company that he dragged in to help, and Jenny who also did a great job. The speakers were ace and the helpers on the day were also really excellent. The main sponsors were my employers, Ibuildings and it was great to have them around for this – and of course to catch up with my colleagues!
In particular I needed dates like “Donderdag 23 Oktober”, and I was sure PHP should know how to do this without me creating arrays for days of the week and months of the year. With some help from my friend (thanks Derick) I discovered that there is a date function in PHP that takes into account the locale of the script, called strftime. The machine needs to have the locale already installed, then you can just do:
setlocale(LC_TIME, 'nl_NL.UTF-8');
return ucwords(strftime('%A %e %B',$publish_date));
Setlocale() will return false if the language isn’t available on the host system, so its possible to check and maybe try a few likely ones or let the user know. This was useful to me and will work for other languages too – you just need the locale installed and then set with setlocale.