Read the latest blogs, news and views from Infomentum. (7)

The highlight of my week? My first MuleSoft Connect 2022! It was the first in-person event in almost 3(!)years. So, in case you missed it, I would like to share what I learned and enjoyed the most during that eventful day.

I've recently had the opportunity to reflect upon our annual staff appraisal process, specifically around the quality of feedback. One frequent observation is that reviews and comments often lack details, making appraisals challenging. It is especially true for managers who don't work closely with the appraisee and rely entirely on their colleagues' feedback to assess their progress. To address this issue, my colleague and I were asked to revisit the process and suggest what could be improved.

'We are planning to upgrade to Mule 4 in a few months. Meanwhile, the development is on hold because it is impossible to find any Mule 3 certified resources. Can you help us?' The head of the integration programme was crying for help. Looks like it is a common problem as many organisations still rely heavily on the old Mule 3 version. 

When the connected digital experience has become "a must" rather than "a nice to be", integration solutions are in high demand. APIs are now almost the de factor way for various platforms and systems to communicate and exchange information. So, what happens when a public API fails? In 2014 Gartner estimated it to be about $300,000 per hour!

How does your team get into the Christmas spirit? With it being the season of giving back, what better way than spending a day helping a local charity! So, when an invitation from MuleSoft came in we didn’t hesitate—helping an urban farm for a day? We are in!

It's been almost two years since our ways of working have changed completely. Although the offices are opening their doors again, online meetings are part of our working life, and they are here to stay.

As a Test Analyst at Infomentum, I generally follow a formal structured test process, one that is promoted by certification bodies such as ISTQB. It ensures that we adhere to the best practices and verify that the software under test meets our requirements. But is it always enough? In my experience, no. On occasion, a more experimental method of testing is a more suitable approach for that given project. Great news, it also fits nicely with an agile development cycle!

We caught up with Sikander Sehrawat, who joined our Development team as an intern and quickly progressed into a full-time Associate position. He talks about what it was like to start his first working experience during a pandemic and his journey to a certified MuleSoft Developer.

We developers love to use and create automated processes! If something is repetitive, we have an urge to write a bash script, a gulp/grunt task, etc. It is in our nature! If we can automate, we will automate.

Exciting news to share! We are launching a new MuleSoft Online Group dedicated to introducing Java Developers to the MuleSoft world.