Does changing your binary storage will cost you some (too much) money ?

Do you have conflicts between your IDE and your build process ?

Bad Execution time

Does your tests run time is too long ?

Does the build take too much time ?

Does your build time take time because you need to package for several environment ?

Does your build time is linked to the number of environment you deploy on ?

Does your build time is linked to the number of language of your application ?

Does your application used several programming languages, and you don’t know how to link them ?

Bad Dependencies management

For some libraries included, do you have no clue where they come from ?

Do you have a library , you don’t know the version ?

Does your configuration files are included in your libraries ?

Does some dependencies among your modules are out of control ?

Is there any transitives dependencies you don’t know ?

Do you need to change your setup generation, each time you change a dependencies ?

Not Helpful

Does your code contains some bugs ?

Do you have a developer not using the same coding practices than the rest of the team ?

Do you have a developer not using the same coding standard than the rest of the team ?

Do you have a developer frightening of doing refactoring ?

Do you have a developer who don’t know (don’t have a vision of) the quality of the code he work on ?

If you answered yes, to one of this question, you have a problem like Mister build. In the next posts we’ll see how a simple and automated build process, following less coupling rules, coupled with a continuous integration framework can help you.

As mister build answered yes to some of the questions … he will stay as a pedestrian for some more days …