Last year, I wrote a post about the problems with code coverage as a metric, and left the topic as “to be continued”, saying that I had some ideas for a better approach. Well, it's taken long enough, but here are the first pieces in that objective to evolve a better way to create and measure well-tested software.
What Makes Good . . .
Yesterday, during the lead up to the WWDC keynote, I started thinking about what really matters the most when it comes to software engineering. We (I include myself) tend to talk a lot about APIs, libraries, features, capabilities and tools as part of our work. And it often feels that making great code depends heavily on use of language . . .