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? We'll take a tour through some processes and tools you can implement to begin improving code quality in your team or organization, and see what a difference it makes to long-term project maintainability. More importantly, we'll look at how we can move beyond today's tools to answer higher-level questions of code quality. Can 'good code' be quantified?
By clicking this button you are declaring that you are the speaker responsible for it and a claim request will be sent to the administrator of the event.
If the claim is approved you will be able to edit the information for this talk.
Great suggestions and finally convinced me to look at continuous integration, even on smaller projects. Also provided insight on things we can start implementing right away to help ensure quality code.
This talk addressed one of those "I want tackle that ... I gotta listen to it!" This was a good high level discussion covering the area of code measurement. The idea of tracking documentation coverage was a new idea for me, so my mind really did get new knowledge out of this one.
Some additional (very specific) examples and/or direction to find additional information might have satisfied my very eager curiosity.
This discussion expanded on some of the other discussions at the event. I think they went together well, where one shared the types of tools, and this one highlighted how these tools can be used to help improve quality of code.
Know of an event happening? Let us know! We love to get the word out about events the community would be interested in and you can help us spread the word!
20.May.2010 at 19:26 by Todd Wolaver
Great suggestions and finally convinced me to look at continuous integration, even on smaller projects. Also provided insight on things we can start implementing right away to help ensure quality code.