Have you found that your code has a lot of bugs even though you’ve invested in maintaining 90% code coverage? Have you also found that your tests break so often that you don’t want to write any more? I have. With multiple clients. Part of the problem is code coverage is a misleading indicator of quality. Even worse, you are writing tests that don’t test anything except the implementation details of your code.
Please take a look at my latest column for Government Computing News where I describe the four technologies that have most revolutionized software development in the last decade–with one notable absence. Just to give you an idea, here is the unedited introduction. In his blog post The Great Works of Software, Paul Ford enumerates five applications that excel in longevity, popularity, and usefulness. Pac-Man made the list, so you know it’s a good one.
There is an episode of Family Guy where Peter Griffin gets a segment on the Quahog 5 News called “What Really Grinds My Gears.” During the segment, he opines on random things that bother him in his own hilarious and offensive way. When it comes to software projects and technology, I have my own list of pet peeves that continues to grow. While not quite as hilarious though potentially just as offensive to some, here are a few.
In the wake of the project management and technology debacle that is HealthCare.gov, I just published my first post on Government Computing News, the leading online publication in federal IT. The topic? Testing is much more nuanced than has been suggested by recent commentary. Developers, testers, and domain experts can work together to leverage a combination of open-source tools, automation and discipline in order to build quality into their applications from the start.