December. The time of year when people stop consuming the budget and start consuming traditional Christmas cakes. However, December is also the time of year to look back and reflect on the previous 11 months.
Public sector customers will now be able to purchase a range of services from digital transformation consultancy Infomentum on the UK government’s G-Cloud 10 framework. We received the news that our application was successful earlier this month, with services going live on the marketplace today.
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:
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.
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.
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.
I was recently invited along to the WPEngine summit, thanks to Infomentum having worked on a customer’s news and views blog using WPEngine and Wordpress.
First of all, I have to say that the entire conference was great. The speakers were well thought-out, and the topics felt fresh - as well as a great goodie bag at the end! But the talk that really captured my attention was by Monica Cravotta. She talked us through WPEngine's latest research: “The future of digital experiences by generation.”
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.
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.
Recently, I was one of the lucky few that were handpicked to attend Oracle's partner training on Intelligent Bot in London - and that meant I got hands-on experience with the product and witnessed its glory in action! The product is called Intelligent Bot and it would be available as part of the Mobile Cloud Service (MCS) suite as it complements other features of that product - not to mention that it fits the product the most. The aim is to provide an easy way to create Chatbot applications in simple steps, and provide options for Intent Recognition - i.e. understanding what the Chatbot's end user means - and custom entities to be able to take actions and drive the conversation towards whatever developers see fit.