
Presented by Nate Abele
One of the biggest problems of software projects is that, while the practice of software development is commonly thought of as engineering,
it is inherently a creative discipline; hence, many things about it are hard to measure. While simple yardsticks like test coverage and cyclomatic complexity are
important for code quality, what other metrics can we apply to answer questions about our code? What coding conventions or development
practices can we implement to make our code easier to measure?