Optimising a pull request for peer review

Last week James wrote a post about the challenges with scaling code reviews in the Java/Backend group here at Brandwatch. In this post I'd like to talk about code reviews themselves, specifically why we do them and how to create a high-quality Pull Request (PR) that facilitates a speedy and successful review. Note: Part of my role here at Brandwatch is stewardship of the Frontend Group, so this post leans heavily on my learnings and experiences with our JavaScript repositories, although much of this post is representative of our Backend Group too. Why do we even PR anyway? Github's »

Server-side rendering of visualisations using NodeJS

The team in Berlin is currently working on automated reporting for our users. We identified a use case wherein users want to check summary information of Brandwatch queries as a periodic report, without needing to log into Brandwatch Analytics to check a dashboard. The Automated Reports product fulfils this use case. Users can log into Brandwatch and set up a report to be delivered on a schedule, and then wait for an email that contains a link to a static report as well as the same report as a PDF attachment. Another time we'll examine how this entire solution was »

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 »