Come and join our well established web development team as a core developer of our PHP based team.
We build and support interactive sites of all kinds, so every project can be very different to keep you and your mind active. You'll be involved with a number of projects at any one time ranging from international brands, enterprise public sector organisations through to charities and media sites. We also run several internal projects which you'll have chance to provide input and development for - this is where we often experiment with new ideas first.
Ideally you'll have 2+ years commercial PHP experience, but also the knowledge of best practices when working as a team on projects.
Come and join our well established web development studio as the lead developer of our PHP based team.
We build interactive sites of all kinds, so every project can be very different to keep you and your mind active. You'll be involved with a number of projects at any one time ranging from international brands to charities and start-ups. We also run several internal projects which you'll have chance to provide input and development for - this is where we often experiment with new ideas first.
Ideally you'll have 4+ years commercial PHP experience, but also the knowledge of best practices when working as a team on projects. It will be your responsibility to take the lead on technical implementation decisions for projects.
Following on from last months initial release of the Cookie Control module for Drupal 7 there has been an increase in blog posts and talk both in and outside of the Drupal world about the implications and solutions to getting sites compliant in time for May 26th 2012.
This week the UK Government revealed that their own sites (some running on Drupal) will not be compliant in time for the deadline! While government websites do not carry advertising, cookies are still used to carry out various tasks, such as helping site administrators monitor levels of traffic.
Whilst doing some R&D around Twitter related services I've noticed holes lacking in APIs for a number of services. It's not just myself that groans, support queues, mailing lists and Twitter are full of people grumbling about lacking functionality from the services.
Today it was the turn of photo hosting service Twitpic who provide a great basic API service but lacks any ability to extract all images for a specific user through the API. A minor bonus is that each user of the service gets an RSS feed of their uploaded images, although it only serves the last 20 images - 20 being the number of photos shown per page.
After another successful year in the land of Drupal we're pleased to be expanding the development team here at Ixis. We're on the look out for two developers to join us on-site in our Daresbury office in the UK. Your work will be based at our new office and travel to clients is not required.
We work in a relaxed and informal environment, where the ability to manage your time and work load independently is important. You'll often be involved in several projects at the same time, although you may be responsible for a website from start to finish depending on work load.
Some administration and debugging modules for Drupal attach their statistics to the end of Drupal rendered pages using PHP's register_shutdown_function function facility. This is great to ensure the output is always available, no matter how badly built the theme being used is.
Examples of modules adding their stats to the footer include the superb Devel package which allows outputting statistics on your database queries (or "Gunk" as its called in the source code), and the Memcache Admin UI module which provides information about the memcache bin usage.
What sort of performance increase would you expect to see by simply using Alternative PHP Cache (APC) and Drupal caching? APC is an extension that caches the compiled PHP bytecode hence avoiding the overhead of parsing and compiling source code for every single request.
The following benchmarks were performed using ApacheBench with 1000 requests (50 concurrently). The requests were sent to the frontpage of the site, which is quite intensive in terms of modules ( views // panels // custom modules etc)