Your developer doesn’t know anything about the code in your app

Well, he does. He wrote it. But he doesn’t know the quality level of that code. So by extension, neither do you as the project owner, and that is costing you a lot of money in wasted development effort.

I remember joining a new project 3 years ago. The application already had lots of features, lots of code and ...

Tons of bugs.

One of my first tasks was to add a search feature in multiple screens of the app. During the planning meeting, I felt confident that it should not take too long since all those screens looked the same. I assumed I could plug create the new feature once and voila the feature would be done in all those areas.

Boy was I wrong! Once I jumped in, I discovered that all those screens were implemented separately.

Worse, each variation was a copy and paste of a previous implementation. This meant that some bug got fixed in one screen, but not the other (because the bug only mentioned that one screen). Does that ring a bell?

And so you’re wondering what are you to do about it. Well, talk to your developer and ask him to set up quality metrics on your code. There are lots of them, some more important than others, but the important first step is to measure, then ask questions about the results and be curious.

You will improve your app quality by paying attention to those metrics.

And when quality goes up, customer satisfaction goes up.

Do you have quality metrics on your code today? Which one? If not, message me, I can help you.