InfoQ Homepage Coding Standards Content on InfoQ
-
Heartbleed’s Aftermath: OpenBSD Developers Start Purifying OpenSSL
OpenSSL's Heartbleed vulnerability has brought the project under the intense scrutiny of the OpenBSD development team. The team began a massive cleanse and repair of the OpenSSL codebase last week with impressive results.
-
Secure Coding for the Android Platform
CERT Secure Coding team, part of the Software Engineering Institute at Carnegie Mellon University, have recently released secure coding guidelines specific to Java's application in the Android platform. InfoQ interviews Lori Flynn, one of the researchers who authored them.
-
Lessons Learned from Apple's GoToFail Bug
The recent security weakness found in both iOS and OS X hints at flaws in coding style guidelines, unit testing, system testing, code review policies, error management strategies, and tools deployment. An overview.
-
Google's Java Coding Standards
Google has recently released their complete definition of coding standards for Java source code. These are hard-and-fast rules that are clearly enforceable, and are followed universally within Google. It covers not only formatting, but other types of conventions and coding standards.
-
Android Stats and Tricks from OpenSignal
One blog of note that is furthering the efforts of today’s mobile application developers can be found at the OpenSignal web site. Their recent Android Fragmentation Visualized report offers some unique perspectives on the challenges of writing Android apps.
-
Using DRY: Between Code Duplication and High-Coupling
DRY reduces duplication and the maintenance problems coming with it, but misusing it leads to high coupling and reduced readability. The lesson: a software development principle should be applied considering other corresponding principles, patterns and practices.
-
Individual Yield
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
-
Is Good Code Enough for a Project to Be Successful?
Simon Brown, a developer, architect and author, considers that it takes a lot more than just good code to create a successful project. In his presentation, "Good Code Isn’t Enough", Brown goes through all the elements necessary for a project’s success, from upfront design to operation documentation.
-
To Comment or Not to Comment
Any developer has written at least one line of comment throughout his code. Some have written many comments in an attempt their code to be more explanatory. This article gathers some of the practices used in writing code comments.
-
Should We Rely on Language Constraints or Responsibility?
Bruce Eckel, Michael Feathers, Niclas Nilsson, Keith Braithwaite, and others on the question: should languages be fully flexible, allowing the developers to tweak them as they like, and trusting they will be responsible in their work, or should there be clear constraints set in the language from its design phase to avoid mistakes that create bad code, hard to maintain or to read?
-
What is Velocity Good For?
A recent discussion on the ScrumDevelopment Yahoo! group discussed the different uses and misuses for velocity. Should velocity be used a metric for productivity? Should it be used for iteration planning? What about longer term release planning?
-
Presentation: The Joys and Pains of a Long Lived Codebase
In this presentation recorded at QCon SF 2008, Jeremy D. Miller shares lessons learned while developing a project over 5 years. He talks about his mistakes, what to avoid and how to design, code and test better.
-
ReSharper 4.5 Beta Promises Better Performance
A few days ago ReSharper 4.5 Beta was released by JetBrains. This new version promise better performance and less memory consumption. New features include VB9 support, native MSTest support, "Go to Implementation" and improved compatibility with F#, Compact Framework and Silverlight.
-
Software Craftsmanship Manifesto: A Call to Arms
A movement to promote Software Craftsmanship has been brewing for a few years. Since Agile 2008 last year they found a focal point with Uncle Bob Martin's claim that the Agile Manifesto needed amending with a new value: "Software Craftsmanship over Crap". Recently a group has created the Software Craftmanship Manifesto.
-
Rewards to Improve Team Habits?
Sometimes teams have trouble starting new habits: writing unit tests, fix compiler warnings, not breaking the build. How do we help the team change these habits? Clint Shank designed a game to help people transition.