“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.” – Brian W. Kernighan.

Everyone tests their software to some extent, if only by running it and trying it out (technically known as “smoke testing”). Most programmers do a certain amount of exploratory testing, which involves running through various functional paths in your code and seeing if they work.

Systematic testing, however, is a different matter. Systematic testing simply cannot be done properly without a certain (large!) amount of automation, because every change to the software means that the software needs to be tested all over again.

This is an introduction to some lower level automated testing concepts, and how to use built-in Python constructs to start writing tests.

In the world of software management there exists a dread place called "dependency hell." The bigger your system grows and the more packages you integrate into your software, the more likely you are to find yourself, one day, in this pit of despair.

This page provides guidelines for version numbering your software.

Ventiquattro ore di programmazione non stop per oltre 2mila studenti di informatica di tutto il mondo. Alla IEEExtreme programming organizzata dall’Istituto degli ingegneri elettrici e elettronici, i pavesi se la sono cavata bene. « Il team dell’università di Pavia miglior classificato è jOmegaTeam – spiega Tullio Facchinetti, professore di programmazione e del laboratorio di robotica del dipartimento di ingegneria industriale e dell’informazione – 

Sonic Pi is a new kind of musical instrument. Instead of strumming strings or whacking things with sticks - you write code - live.

By Derick Bailey

Most professional software developers understand the academic definitions of coupling, cohesion, and encapsulation. However, many developers do not understand how to achieve the benefits of low coupling, high cohesion and strong encapsulation, as outlined in this article. Fortunately, others have created stepping stones that lead to these goals, resulting in software that is easier to read, easier to understand and easier to change. In this article series, I will define three of the primary object-oriented principles and show how to reach them through the five S.O.L.I.D. design principles.