As an organisation there has been a bias towards deliver, deliver, deliver! NAP over the years has achieved huge success, we have added more brands, theOutnet.com, mrporter.com and more recently expanded into APAC. Achieving this growth, coupled with tight deadlines has paradoxically impeded business responsiveness.
The 6th London Software Developer in Test Gathering will be held at THE NET-A-PORTER GROUP offices on Thursday 6th March, between 7:00pm and 9:00pm.
There will be three talks, as well as the opportunity to discuss the latest technology and topics affecting developers in test.
The Product Management team recently built a new Catalyst Perl application and we wanted to ensure that we would maintain a high level of code coverage in our test suite. This seemed like an ideal opportunity to use Devel::Cover; we currently use Jenkins to build all our branches, and Devel::Cover allows us to integrate easily with Jenkins to run the coverage report after each build.
In a perfect world, all the data pertaining to a certain domain would
be authoritatively held and edited in a single place, and everything
else would refer to that place as the source of truth.
We just released Assembler – a plugin for Backbone that makes it easy to manage nested views.
Assembler was initially written to solve the need for rendering nested views server-side and re-attaching them client-side in a
node.js/Backbone application. However, we also found it useful for quickly mocking up apps and prototypes as well, so we’ve decided to release it as a standalone library.
Or is it?
It’s not so much the act of estimation that’s the issue. We accept that estimation can be a useful tool to help teams gain a shared understanding of a work item, and to break work down. It’s what we do with those estimates afterwards that matters. Other than the value to the team, the most common reason for doing any estimation is in an attempt to be predictable: we want to be predictable so that we can budget for projects, and provide our stakeholders with some understanding of the progress of those projects.
At a recent meeting, some ideas for an office event were being discussed, and people were considering hiring a photo-booth for the evening. I had a huge lightbulb moment: we’ve had a photo booth in the office and at some staff events already — why do we keep paying other people to do this? Surely we can create our own for a fraction of the cost?
How hard can it be?
This is the question I set out to answer in our most recent Hack Day.