coder . cl

Managing changes is really important in software development projects. Each change should be handled carefully and must not be seen as part of the original development process. Instead, you should measure and control each change in the original requirements, even if you are using agile or cascade methodologies. You cannot accept all changes that the customer proposes without the proper management process. Is not that easy to handle changes in requirements like changing a comment in the code. Instead of accepting changes and delivering software without the proper management process, you should be able to handle those requirements using a standard method to manage those requirement changes.

Communication is key element for successful projects. So, you should report bugs properly to eliminate them and you should be very careful describing them. There are some mandatory elements that should be supplied on bug reports, using some templates that provide enough information to let the developer know how to handle its solution and let him to know how to omit new bug creation. A good bug report should clearly display the right information, and we can classify them in three types, as functionality bugs, programming bugs and technical bugs.

«What is your preferred language?» is a good question I think. From its paradigm to how it should be indented is a good approach to select a language based on the preferences of your programmers. Few days ago I have launched a public poll related to what is the preference in programming language between the people that I meet in social networks. I am very glad to see up to 150 responses to the poll and I am very glad to see that most users have a preference for strictness, rather than fully freedom. So, here are the results of that poll.

The fact that many project managers are guided by the cheapest price and requiring «low profile» developers is generating a good percentage of software pieces that can be honoured with the most hilarious posts in The Daily WTF. Also some hiring head hunters which are not able to handle technical resumes because they have no idea about software development, is subject of some gags. No matter how good is a developer, if he does not place numerous times that cool technology which is subject of the job position posted on that prestigious newspaper, he will not be selected and probably that is not a good company where to work.

When to add unit tests?. All depends on how are defined the requirements. If the requirements are well defined, you can add tests on every step in the development, doing evolutionary tests. But if you are working with dynamic methodologies like agile ones, you should add tests only once a requirement is correctly defined, otherwise you will be adding unit tests twice. So, each requirement should have its unit test suite as companion to check that the added feature is working properly.