Better Software Magazine
Better Software Magazine Articles
|
Encourage Pair Programming Pair programming is one of the most controversial agile practices. Managers are concerned about the costs and developers are concerned about personal agony. But there also are many benefits. If you are thinking about trying pair programming, here are several reasons why you should. |
Rob Myers
June 24, 2008 |
|
|
Software: Use at Your Own Risk Is it really so hard to produce software that works? When was the last time you read a software license agreement? Most are one-sided statements that limit the product developer's liability. It's time to move away from "Use at your own risk" software and be upfront with customers about the true cost of quality. |
||
 |
Give Your Defects Some Static Computer security has raised the demand for automated tools that can analyze source code for vulnerabilities and defects. Find out how you can put automated static analyzers to work for you. |
|
 |
A Galaxy of Patterns The Gang of Four's design patterns have a special place in many programmers' hearts. But it's time to look beyond the GoF twenty-three and realize they aren't the only patterns in the universe. |
Neil Harrison
June 24, 2008 |
|
How to Fail with Agile A switch to agile often conflicts with personal career goals such as maintaining the status quo and working no harder than necessary. These twenty guidelines will help you sabotage your agile project, helping you fail quickly and spectacularly. |
||
|
How to Fail Less and Enjoy More The shiniest software application in the world, shipped on time and under budget, is a failure if it doesn't make someone's job easier. Failures cost us customers and money. How can we design software that our customers want to use and that will reduce our cost of failure? |
Frédéric Boulanger
May 30, 2008 |
|
 |
Advice for the New Leader As a new manager it's easy to fall into the trap of taking on more of your team's responsibilities than you should. Learn how to guide your team to success by stepping back and letting team members solve their own problems, learn from their mistakes, and most of all do what you hired them to do. |
|
|
The Mission Is the Message A mission statement is supposed to guide and inspire the members of an organization as well as define the organization's purpose, the business it is in, and its responsibilities to its clients. Is your statement sending the right message? |
||
 |
Stop The Insanity! Using Root Cause Analysis to Avoid Repeating Your Mistakes We've all heard Einstein's definition of insanity, and it definitely holds true in software development. We "are" going to make mistakes in product development, but root-cause analysis can help us understand those mistakes and be proactive in not repeating them. |
|
 |
The Myth of Risk Management Risk management is an illusion. We must recognize that software projects are inherently risky and admit to ourselves that it's not the known problems that are going to cause our projects to fail. It's the risks that are unmentionable, uncontrollable, unquantifiable, or unknown that make projects crash and burn. |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.