Rinat Abdullin

Development seems to evolve quickly when the D.R.Y. principle is enforced

One starts his development career with simple WinForms applications, then gets to the web applications.

80% of projects’ functionality is being delivered with controls and code here.

All is well.

But then the project complexity keeps on growing along with the experience. And in order to be able to develop and maintain solutions while having only limited resources at hand, one has to learn patterns, start using IoC and different efficient development techniques, get rid of the repetitive code.

80% of projects’ functionality is being delivered with components, services and their configuration here. Coding, obviously, remains, since one still needs to cover 20% with custom code.

All is well.

But then project complexity keeps on growing along with the experience. And in order to be able to develop and maintain complex systems while having only limited resources at hand, one has to learn common business patterns, start using multi-scoped IoCs, do even more efficient stuff, start encapsulating complex inter-component logics into modules to avoid doing repetitive coding and configuration. It all leads to doing more development by configuration instead of development by coding.

80% of projects’ functionality is being delivered with modules and packages here. Working with raw components, services and configs, obviously, remains - since one still needs to cover remaining 20%. And 20% of these 20% still require actual coding.

All is well.

But then the project complexity keeps on growing…

No comments yet.

Leave a comment