BT
Older Newer rss

Cool Code

Posted by Kevlin Henney  on  Feb 09, 2012 2

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Beauty Is in the Eye of the Beholder

Posted by Alex Papadimoulis  on  Feb 06, 2012 4

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

How to Stop Writing Next Year's Unsustainable Piece of Code

Posted by Guilherme Silveira  on  Feb 02, 2012 10

Guilherme Silveira mentions some of the turning points in project development that may affect the quality of the code offering advice on avoiding writing crappy code.

Stop the Software Architecture Erosion

Posted by Bernhard Merkle  on  Sep 16, 2011

Bernhard Merkle advices on preventing architectural degradation of a project by using tools for constant monitoring of the code, exemplifying with an analysis of Ant, Findbugs and Eclipse.

Infinitely Extensible

Posted by Alex Papadimoulis  on  Aug 31, 2011 1

Alex Papadimoulis discusses avoiding over-engineering a program, presenting extensibility types used, extensibility design patterns, when to use them, and what happens when they are incorrectly used.

Software Quality – You Know It when You See It

Posted by Erik Dörnenburg  on  Aug 30, 2011 1

Erik Dörnenburg explains how to use various visualization tools to spot patterns, trends and outliers in the code that are an indication of code quality level.

Compile-time Verification, It's Not Just for Type Safety Any More

Posted by Greg Young  on  Jul 05, 2011 9

Greg Young talks about .NET’s Contracts library, showing how to use it, what it is good for, and how it improves code quality.

Where Did My Architecture Go?

Posted by Eoin Woods  on  Jun 22, 2011 2

Eoin Woods advices on writing code that preserves the initial architectural design using conventions, dependency analysis, module systems, augmenting the code & checking rules, and language extensions.

Five Static Code Audits Every Developer Should Know and Use

Posted by Mike Rozlog  on  May 17, 2011

Mike Rozlog discusses the need for software audits, proposing five code reviews that every developer should use: Numerical Literal, String Literal, god Method, Shotgun Surgery and Duplicate Code.

Living and Working with Aging Software

Posted by Ralph Johnson  on  Sep 01, 2010 1

Ralph Johnson discusses principles, practices and tools relating to software development starting not from scratch but from already existing code which needs refactoring, maintenance, and sometimes architectural change.

The DCI Architecture: Lean and Agile at the Code Level

Posted by James Coplien  on  Jun 30, 2010 3

James Coplien explains the DCI (Data, Context, Interaction) paradigm used to better represent the user’s mental model in code through system state and behavior. Coplien makes an attempt to reintroduce architecture to Lean and Agile projects due to its value in sustaining high velocity and change resiliency.

Scrub & Spin: Stealth Use of Formal Methods in Software Development

Posted by Gerard Holzmann  on  Jun 02, 2010 1

Gerard Holzmann discusses Spin, a design analyzer tool, and Scrub, a code review tool, used by Jet Propulsion Laboratory to analyze and fix the software used for critical solar system exploration missions.

General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2014 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT