Skip to main content

My first couple of weeks at Readify

So now I've been at Readify for a few weeks and it has been great. If you gave me a few words to describe Readify I would say:
  • Quality
  • Learning
  • Smart
  • Agile


There is a different dynamic working here for Readify as a consultant. As a consultant, one is not a employee of the business, but rather someone who provides a service. This change of mentality creates a different relationship all together between the developer and the product owner. Including things such as: more autonomy for the development team, a higher responsibility on the team lead and generally higher quality software. It creates a win-win situation for all. 


Readify development teams do Agile VERY well. Prior to starting with my first client, I was observing a team at the Readify office using a hybrid scrum-kanban methodology for their project management. I noticed instantly that all team members were aware of the workings of Agile. In addition to this, a CI pipeline was setup that linked to a build light. All these agile processes allowed members to get a feel to how well the team is progressing.

Many of these practices that I had tried to set up at my previous places of employment (and I was only slightly successful) had been fully implemented at Readify. What made me even more happy was the success that these processes were providing.

Constructive Feedback

Readify is a place where people aren't afraid to give and receive constructive feedback. In fact, the culture instilled into the Readify environment ensures that it is everyone's responsibility to ensure that all other Readifarians are given the feedback they require for improvement.

Communication Skills

As a developer consultant at Readify, I am not only required to have excellent technical, engineering and development skills. But also, build my business, managerial and communication skills. I estimate about 70-90% of a Readifarian's life would be technical and the other would be these soft skills. Readify not only builds great developers but great entrepreneurs and thinkers in general. 


Perhaps the biggest reason why I joined Readify was because I will be able to learn from the smart people around me. I can say that after about 5 weeks that I have not been disappointed at this expectation. The mentoring that I have received in these last 5 weeks and the support from the other consultants has been invaluable. Readify has a ton of people who have been in the industry for 10-15 years (I mean IT has only been around for 20 years anyway), their wealth of knowledge has provided me so much insight.

Readify has been great so far, and I can see myself developing many skills here. I'm looking forward to the great adventures, experiences and challenges that are to come!


Popular posts from this blog

from zero to production in eighty days

When I mean zero, I literally mean zero. A brand new project, a PO that's new to IT, no existing processes in place and a small team of four including myself and the PO.

The departmental organisation we were working for doesn't have any developers, scrum masters, product owners working for them. Everything they did was either done by another department or outsourced completely.

This is a story how we went from zero to production in eighty days.

My first time speaking at a conference

Since time immemorial we humans have valued the art of public speaking. Today, I want to share with you my experiences in speaking at conferences for the first time. Recently, I spoke at both DDD Melbourne and DDD Perth. Both of which were positive experiences that I learnt a lot in.

Have You Ever Produced Negative Value in a System!?

As developers we encourage our product owners to order the priority of their backlog in order of value. However, every time a new feature is implemented by a development team, there is a certain degree of risk associated with the introduction of that new code. Namely, risk of breaking another part of the product and maintenance cost. When a development team pulls in a new feature to implement there is a certain acceptance of this risk. In many cases, the risks that arise due to additional code complexity doesn't justify the value added by the new feature itself, so the development team can start implementing it.

Are there scenarios where the value added to a software product can be negative though?