Headless WordPress with React & Gatsby - Part 2: Implementation

By Nick Bishop on Jun 13, 2018

Part 2: Implementation

In Part 1, we talked about picking the tools for our first foray into the world of headless Content Management System (CMS) architectures, during our project with Fudgelearn. We had other options on our radar, but we decided that WordPress was the CMS that fit in best with our requirements. These were the main ones:

Continue Reading

Headless WordPress with React & Gatsby - Part 1: Choosing our tools

By Nick Bishop on May 31, 2018

Web development is accelerating at an incredible rate - new frameworks seem to pop up every day. Whilst this is exciting (at least to a front-end geek like me!), it can be difficult knowing which new tools are any good and which ones you should be using.

Continue Reading

Submitting a question to Java Challenge UK

By Shaha Alam on May 23, 2018

A few weeks back, I decided to get involved in Java Challenge UK, by sitting on the competition’s jury panel. A bit of context: the Java Challenge is a gamified competition, with one league for professionals and one for students, that consists of multiple-choice questions. As part of the “jury duty”, I had the task of writing one of these questions. I decided to write my question around lambdas; read on to find out a little bit about why...

Continue Reading

Powering your Cucumber Acceptance Tests with Jira Integration

By David Weston on Apr 11, 2018

In my last article, The evolution of test documentation; lessons learned from implementing Cucumber, I explained two things. Firstly, how we at Infomentum have adopted Behaviour-Driven Development to define test scenarios, and secondly, how we use Cucumber JVM as an implementation platform for running these scenarios as automated tests.

Continue Reading

DevOps: cultural reconstruction

By Luke Rixson on Dec 7, 2017

A wise man once said "If you are going to dive head-first into DevOps, better pack a parachute". Aside from the fact that this man was me, the point is still valid. 

Infomentum had started maturing into a DevOps culture, which involved the developers using tools normally associated with DevOps to solve development problems. We were calling it DevOps for several years, even though the actual DevOps culture, practices and support were not in place. The changes made were effective at enhancing the development lifecycle, but were completely separate and sliced off from the rest of the organisation. This meant that infrastructure needed to catch up so that the DevOps practices could be fully utilised throughout the company. The major issue with DevOps is that it really is all or nothing; as soon as you have segregated processes and half-utilised technologies, the power of DevOps is completely negated.

Continue Reading

A day in the life of…a development intern

By Infomentum on Jul 28, 2017

Kicking off our new blog series, ‘A Day in the Life of…’ our summer interns, computer science students Pratik Jadhav and Hasan Rafiq, reveal a behind-the-scenes glimpse of an intern’s typical day.

I chose to study computer science because…

Pratik: My dad is in the IT business so it’s something I’ve been interested in from a young age. I love technology and I wanted to understand how everything works, and how to develop everything.

Hasan: Other members of my family are in IT so I always knew about it. At first, I was going to go into dentistry, but I tried it out and I couldn’t see myself looking into other people’s mouths for the rest of my life! So I knew then that I wanted to go into computer science.

Continue Reading

The evolution of test documentation; lessons learned from implementing Cucumber

By David Weston on Jul 14, 2017

The old way

I'm going to let you in on a secret. I learnt my trade in a traditional software testing consultancy - I'm talking a waterfall approach to test planning, test case definition and test scripting. Over the last 5 years at Infomentum, I've evolved and have worked hard to optimise Infomentum's testing practices to suit our agile development environment. 

Continue Reading

Nightmare on time sheet; how we overhauled the time logging process (part 3)

By Becky Burks on Jun 29, 2017

Wait: you need to read part 1 and part 2 first!

The fun side of cultural change

You’ll remember that last week I discussed the crucial need for a cultural change in how we dealt with time logging. After the CX team’s thorough research, we were ready to take the findings – and our ideas – to our board of directors. 

Continue Reading

Nightmare on time sheet; how we overhauled the time logging process (part 2)

By Becky Burks on Jun 22, 2017

Hint: you'll need to read part 1 first for this post to make sense.

Phase 2: Imagine

The CX team got together to discuss the problems and carry out an internal ideation workshop to tackle them. We knew that we had 3 key tasks:

  • Improve people’s knowledge of why time logging is important
  • Create a culture of time logging as a habit; and
  • Make the systems they needed to use simpler and clearer while having less of them!
Continue Reading

Nightmare on time sheet; how we overhauled the time logging process (part 1)

By Becky Burks on Jun 15, 2017

It had been coming for a long time…

At the end of every month, developers scrambled to complete their timesheets, while the operations team were breathing down their necks, threatening them with sticks to get it done - and done right. The developers were left wondering why operations wanted their time logs so desperately. Surely they already knew what they had been working on? The operations team were scratching their heads as to why the developers didn’t do it; they had been reminded at the end of every month like clockwork, yet every month the same story. It was hugely frustrating for both sides, and was approaching boiling point. As soon as the Customer Experience team had a break between projects, we knew this was a top internal issue that had to be solved.

Continue Reading