InfoQ Homepage Coding Standards Content on InfoQ
-
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.
-
JetBrains Releases ReSharper 4.0 with Many Improvements, C# 3.0 Support
JetBrains has released the much-anticipated productivity Visual Studio add-in, ReSharper 4.0. Resharper 4.0 includes many improvements and new features.
-
StyleCop – Microsoft's Style Enforcement Tool for C#
Style enforcement has long been a hotly debated topic. Not only are their arguments over what style a team should standardize on, but also on whether or not there should be a standard style at all. In a move that is sure to add fuel to the flames, Microsoft has released StyleCop, the style enforcement tool they use internally.
-
Review Board - Online Code Review Tool
Recently there has been a resurgence in interest in code reviews. InfoQ looks at Review Board, an open source application that helps facilitate the code review process, that has been gathering momentum in the open source community.
-
Opinion: Programming Languages Shouldn't Enforce Style, Teams Should
Some believe that, if you write a large enough cookbook, there will always be a simple recipe to solve our programming problems. Taking it to an extreme, some want programming languages to limit developers to safe constructs and clean style. Reg Braithwaite skewers this idea, and challenges teams not to give up accountability for style, asking "Whatever happened to code reviews?"
-
Are You An Agile Architect?
Vikas Hazrati recently posted an article on Agile Journal, defining his ideal characteristics of an Architect working in an Agile team, reflecting how the role of Architect has changed in light of Agile practices.
-
Peter Hosey of Adium on Code Reviews
There is no question that formal code reviews catch bugs and can delay the inevitable "big ball of mud" that all successful projects seem to turn into. However, arranging a meeting for every check-in quickly becomes untenable on all but the most critical of projects. Peter Hosey talks about his experiences and how he conducts code reviews in Adium.
-
-
Explicit vs. concise code in Ruby
Ruby offers many ways of reducing code size. However, this can backfire in some situations. We look at one problem with Ruby's method for identifying nil and false values.
-
Google SoC Series: dcov - Ruby documentation coverage analyzer
Ruby gains another tool to ensure code quality: dcov analyses Ruby code and determines the documentation coverage. We caught up with dcov developer Jeremy McAnally to talk about his plans.
-
Seven Deadly Sins of Programming
Eric Gunnerson, C# Community Coordinator at Microsoft, has posted his list of the Seven Deadliest Sins of Programming: * Excessive Coupling * Inappropriately Clever Code * Deferred Refactoring * Premature Optimization * Overuse of Virtual (C#) or Overridable (VB.NET) * Overuse of Inheritance * Premature Generalization
-
Debate: Public Fields and Naming Conventions
Jeff Atwood's blog post earlier this week has stirred up debate in the .NET community on properties vs. public fields and naming conventions for .NET. After first suggesting to use public variables in place of properties, Jeff retracted this suggestion. Also at issue, using case to distinguish public properties vs. m_ or _style-prefixes, and SCREAMING_CAPS constant declarations.