Frequent, small releases help ensure constant communication and tight feedback loops.
Technical debt is a metaphor for all of the shortcuts, hacks, and poor design choices made for a given software system that compromised its quality, usually in an attempt to meet a deadline. It can be an appropriate business decision … Continued
An XP Practice.
Continuous Integration is an XP practice that ensures problems with the full system are detected as soon after they are introduced as possible. It refers to automatically building and testing the full system (integrating the system with all of its … Continued
An XP Practice, Whole Team refers to the idea that the team involved in building an application or delivering a project is the whole team. If the project needs UI design, or testing, or data modeling, the individuals with those … Continued
It is hard to overestimate the importance of choosing good names for source code elements in software development. Much has been written on this topic, and it is often a source of great debate. “What makes a name good, or … Continued
Test Driven Development, or TDD, also known as Test Driven Design, is a process for writing code using tests to define and then confirm the software’s behavior. It is characterized by a set of steps known as “Red – Green – … Continued
Writing code that is readable is critical for any software application that needs to be maintained for any length of time. There are valid performance and anti-theft reasons tominify or even obfuscate code that is being deployed, but the source … Continued
A practice of XP and Agile Teams.
Don’t just code with blinders on – understand how what you’re building will be used and the problems it’s meant to solve. As developers, it can sometimes be tempting to focus purely on the technical, engineering challenge of the task … Continued