Top Stories published by Capgemini Engineering in 2016

How to write effective bug reports

Unfortunately, software will always have bugs, and those defects need to be tracked. Whether you’re doing automated or manual testing, when that testing finds a problem, you need to communicate that problem to the development team. The way to communicate it is by…


How Not To Lead A Team

In my previous article about good lead developers, I said that there was another story, about some of the bad leaders I’ve worked with. Well, it’s time to tell that story.

Initially I was reluctant to focus on the negatives, but it’s just as instructive to look…


Considerations for a Drupal 8 upgrade

If you’re migrating from a different CMS platform, the advantages of Drupal 8 seem fairly clear. But what if you’re already on Drupal? There has been a lot of discussion in the Drupal community lately about upgrading to Drupal 8. When is the right time? Now that…


React-ing to change

With the recent release of the ‘The State of JavaScript’ the clear big gainer of 2016 is ReactJS. So what’s all the fuss about? I’m going to look at the two big boys in the front end space. Angular and React!

The Fairy Tale


What to look for in a code review

In a previous article on this blog, I talked about why code review is a good idea, and some aspects of how to conduct them. This time I want to dig deeper into the practicalities of reviewing code, and mention a few things to watch out for.

About
Capgemini Engineering
Capgemini Engineering team blog: Opinions expressed on this blog reflect the writer’s views and not the position of the Capgemini Group. https://capgemini.github.io/
More information
Tags
Editors