Development at Brandwatch: Our First Code Retreat

This post was originally published on Brandwatch's main blog on 5th September 2014. At Brandwatch we’re constantly challenging ourselves to improve our development skills. We’re happy with some of approaches we’ve taken so far: we started reading groups, run weekly technical talks, and have Funky Fridays every two weeks. Last week we decided to explore another avenue – we hosted a full-day workshop, using the Code Retreat format for our entire development group. What is a code retreat? A code retreat is a day-long intensive practice workshop that focuses on the fundamentals of software development and design. It »

Say Guten Tag to the Queries & Dashboards Team!

This post was originally published on Brandwatch's main blog on 29th August 2014. First of all, let me introduce you to Brandwatch’s Q&D team: that’s Shaun, Sebastian, Thomas, Kentaro, Łukasz, Claudio, Fernando, Mélanie, Stefan, Judith and myself. Above: Our team giving ‘Padel’ a go earlier this summer – an easy to pick up combination of squash and tennis Most of us are based in the Stuttgart office (main office language: English with a bit of swabian mixed in), while three of our team members sit in our other offices in Berlin and Brighton. What’s nice regarding »

Responding to Change: Introducing MVPs

This post was originally published on Brandwatch's main blog on 22nd August 2014. The Engineering team here at Brandwatch have an ever-growing wishlist of features and functionality to add to our platform and products. It can be difficult to decide where to allocate development time, so we’re continually exploring new ways to gauge what adds the most value for our users. Introducing MVPs One concept that we’re currently adopting is to initially create features as Minimum Viable Products, or MVPs. Wikipedia succinctly summarises the concept as: “In product development, the minimum viable product (MVP) is a strategy used »

Quaid, Start the Reactor!

This post was originally published on Brandwatch's main blog on June 16th 2014. We are the Reactor team. Unfortunately we do not look after nuclear reactors (no matter how much we dream) although we do have 3 Ph.D. engineers on the team. What do we do? Well, Reactor is one of the key use-cases that the Engineering team wants to build software for. A Reactor wants to know the latest and most important information right now. They don’t care about noise. They’re busy people, and they want to react to a crisis before it happens, not afterward. »

Accelerating Design Solutions with Design Sprints

This post was originally published on Brandwatch's main blog on 15th August 2014. A couple of weeks back we ran our first full-fledged design sprint. We sketched, brainstormed, wireframed and storyboarded and discovered many new avenues to explore but also learnt a lot about running design sprints themselves. In the engineering department we work to constantly to fix bugs and develop new features so as to improve the experience that you have with Brandwatch software. Once in a while we break away from this and try to do some big picture thinking. What would be new features that our users »