Recently we moved Net-A-Porter to use a dynamic product image service created by our Product Management team. Not only will it allow us to improve our customer experience but it will decrease the time to get products to market.
MRP (Mr Porter) and TON (The Outnet) had already implemented the system but at NAP (Net-A-Porter) we were waiting for a few additional features, and also see how it handled the other brands.
Previously NAP had all of the image assets mounted to the web servers with a CDN sat in front, allowing for them to be served extremely quickly. We wanted to make sure that the service creating and storing the images for us wouldn’t degrade performance for our customers.
We wanted to be able to collect performance metrics to compare NAP image performance to the other brands. I created a simple tool to test different image requests in bulk and collect the average response time.
Deployment can be a tricky topic to tackle. You want ease of use, reliability, speed and consistency, right?
After my previous visits to Sauce Labs, Google and Keen.io, it was finally time for the main event. I was lucky enough to get tickets for Google I/O through some of the Polymer work we had done over the last year. As I mentioned in part one I have never been to San Francisco before, so I didn’t have a previous I/O to compare it to. However, I know they changed up the format this year, giving it a more “festival” vibe — I assume to differentiate it from other conferences and be more “Google”.
I’m going to cover the bad, the good, the highlights, and the things I learned.
If you don’t know about Keen, they are an awesome platform, providing analytics for developers. In this post, I’ll show you a couple of ways we’ve used Keen IO, as well as bringing you video of the talk I gave about it during my visit to Google I/O 2016.
Here at YOOX NET-A-PORTER, we think that testing is an important part of a modern development process. As a new starter in a team working on Scala APIs that provide up-to-date shipping options information, I wanted to write about ideas we’ve discussed on how we write test code. Writing good test code can be as much of a skill as writing good application code, and our team have been looking at tools and frameworks to help us with writing the most readable, reliable and efficient test code that we can.
As the first hackathon for the combined YOOX NET-A-PORTER GROUP kicks off in our development centres of Bologna and London, I’d like to explain why NET-A-PORTER ran internal Hackathons for several years, and why we’ll continue to do so as the YOOX NET-A-PORTER GROUP.