Continuous Integration (CI) is a process that allows developers to integrate, in a repository share by the entire team, code developed by himself, at least once a day. At an Utopian Universe, those integrations should happen several times each day, basically every time some code is “pushed” into the repository. This action will trigger the automated process.
Continue reading “Continuous Integration”
The pair programming process is a work methodology advocated by eXtreme Programming (XP). As the name implies, each programming unit consists of two developers on a single computer. We may incur in the wrong thought that it is a waste of human capacity, since there are two elements to accomplish one’s tasks. However this thought could not be further from reality.
Continue reading “Pair Programming”
IBM championed the code review process since a long time, in fact since 1974. It was initially defined as a “code inspection”, a formal static analysis process to evaluate if the software was full-filling the requirements. This process was slow but, even so, IBM enabled to obtain significant quality improvements in the delivered code.
Continue reading “Code Review”
[Edit: Added info concerning mutation tests (31-01-18)]
The “eXtreme Programming” methodology promotes the test-driven development approach (TDD). What that means?
It is common to see a developer jump headfirst into a functionality. However, TDD advises otherwise.
Continue reading “Test-Driven Development”
Are you one of those developers that use to write code in some sort of cypher, whose only you understands, afraid of being ripped off of your code or seeing your job terminated?
Hopefully you will read this through because I have bad news to you.
Continue reading “Coding Standards”