Mostly Software Engineering

I have just published a new paper under the “Good Coding Practices” section, which I think can be useful for someone else.

In this article I classify the bugs depending where in the life cycle of development they can be produced. This would be helpful to reduce the bugs which can be produced in the softwae development and will help if any bug appears since we know, just with its behaviour, where in the life cycle was produce. Therefore we will be able to react sooner and fix it in less time.

This is the base of comming papers about building secure software systems from a software engineering point of view.

Besied the PDF and HTML versions I always provide this time I have the Google version as well.

This is quick review of the article written by Martin Fowler about Continuous Integration, which basically explains that you should use a control version system and commit and build every day.

I only find, the advice regarding the periodicity of the commits and builds, not right at all since I think it would much better building a few times a day rather than a build per commit.

So I propose a fixed building times spread over the working hours which, as I explain in the paper, leads to an improvement of the productivity while keeps the developers happy, which I think is a must for all the project managers.

You can find the article in the Good Coding Practices section or get the pdf just here.

UPDATE: HTML version available!