Any code is being written by a developer, on his development machine. This is where it all starts, this is where things can start going wrong or, on the contrary, where the quality gets built in.
There are practices, which prove to help writing exactly the code needed, the code maintainable and transferable to other developers. Here are just a few of them:
- extreme programming
- pair programming
- test-driven development
- behavior-driven development
- domain-driven design
- aspect-oriented programming
- object-oriented programming
- design-by-contract programming
Any of them and others serve specific purposes, work best in one environment and do not work in another. What to use? what to postpone? how to use correctly? We can help.
And what then? Then the code changes in the source control repository and can be automatically and very frequently checked against all other simultaneous code and configuration changes: code changes are being integrated.