Have you ever been frustrated with code that is sprinkled with poorly named classes, methods, and variables? One of the most valuable things you can do as a software developer is to choose good names and to sensitize your teammates to the benefits of improving names.
Most people hate making decisions, and are afraid to make the wrong decisions. This is in my opinion one of the root causes why we have so much horrible software.
Avoid using defect tracking systems during the iteration. Fix bugs discovered in the work underway for the iteration immediately. If it takes a lot of work, create a task in the Spring backlog. However, there is usually no need to log this bug in the defect tracking system. Logging it …
Wikimedia software developer and Software Craftmanship advocate Jeroen De Dauw discusses about how to maintain code. A significant amount of time is spend on reading code, sometimes more than on writing code.
Minimalism also applies in software. The less code you write, the less you have to maintain. The less you maintain, the less you have to understand. The less you have to understand, the less chance of making a mistake. Less code leads to fewer bugs.
Code reviews and software inspections have existed for a long time in the software engineering world. They have been however only adopted by a minority of software development projects. Programmers have always been reluctant to submit their code to the criticism of their peer. The pair programming technique promoted by …
