In this blog post we want to share some tips & tricks for deploying with capifony which you might find useful as well.
As discussed in one of my last blog posts, we really like New Relic for performance metrics and use it a lot. Unfortunately there isn't an extension for HHVM (yet) and HHVM is becoming an important part in our setup. But - a big great coincidence - New Relic released an Agent SDK and with that, an example extension for HHVM and WordPress. That was a great start for me to get behind the whole thing.
Liip has a lot of employees that start their IT career with us. We invest heavily in helping them grow, not only in terms of coding but also in other aspects. For example since we essentially have no hierarchy in teams, young developers can very easily take on new responsibilities. All they have to do is build up the trust within their team rather than having to convince upper management to give them a new title, just because they want to try out a new role in a project. We are also very proud of the top 10 rating we have in terms of employee happyness. At the same time we have noticed a certain pattern that after 4-5 years with us, many of these young developer built up a certain "wanderlust". They want to see how things are out there. A while ago I had already formulated the idea of an exchange program to address this need on my private blog. While talking to fellow Liiper Nadja, we have now matured the idea a bit more, which let me to sending out a short tweet that managed to get over 30 retweets in less than 12 hours: "looking for a non-swiss web product company to partner with @liip on a exchange program to give junior devs a chance to explore the world."
Anthony posted a very interesting opinion piece about the future of PHP. I want to specifically comment on the part about HHVM and Hack. I have of course published my own opinion on the topic fairly recently on my private blog. Fellow Liiper Chregu has also done a very popular post on this very blog showing some very significant performance improvements that can be achieved with HHVM. Infact the project Chregu is working on is looking to be one of the first large production users of HHVM outside of Facebook and he is making good progress on integrating HHVM with New Relic which we use quite a bit for performance analysis in larger projects. Facebook is also presenting their point of view on PHP and Hack and probably the most promiment was this presentation called "Taking PHP Seriously". So with having set the stage let me address some of the points raised by Anthony.
One of our currently bigger projects is soon going online and one part of it is an API, which only delivers JSON and XML to a lot of possible clients. To speed things up, we use varnish in front of the application (a lot of requests are easily cacheable, since they only change once a day at most). We also use HHVM for some of the requests, for now just the ones which will have many misses (from livesearch requests for example). We don’t dare yet to use HHVM for all requests, we’d like to gather some experience first with it.
This is the last and final part of the blog post series on Multi-Device Interactions. Previously, I outlined the second-screen trend in TV industry (Part 1) and introduced some underlying models in our multi-device world (Part 2).
In this blogpost we (finally) focus on the practicalities of Multi-Device Interaction Design. It indeed has become a challenge for User Experience Designers to develop solutions that account for the multi-device behaviour of today's user. As mentioned earlier, we have developed a canvas to think and design multi-device interactions. The Multi-Device Interaction Canvas (MDIC) is a modifiable and simple canvas to map multi-device use cases. It bases on the theoretical models we presented in previous blog posts.
At its core it respects three important factors:
The first alpha version for the next major PHP release was made available last week. A list of the new features is available at php.net
Liip has a tradition of company-wide gatherings. As a company whose office locations are spread across Switzerland we want to make sure people know each other, and of course we also want to benefit, as a company, from the knowledge we constantly create with our work in Lausanne, Fribourg and Zürich.
One of the formats we find useful is the Techday, a yearly event where we learn about technical or business topics during the day, and celebrate together at night. This time, however, we thought that opening that format up and share forces with our friends from Mayflower could make it even better. They operate in a very similar way as we do, but are located in Würzburg and München, Bavaria.
In our last blog post we started off with John’s story to show the everyday encounter of multiple devices and screens, and outlined the emergence of the second screen business. The classical second screen solution is a companion app for mobile devices that delivers additional information to TV content, e.g. a quiz or sport statistics on your smartphone or tablet. With all the possibilities in a multi-device world, it’s crucial to focus on the conductor of all these instruments - the user! In the following sections we dive into some theoretical models on multi-device interaction.