Home > Articles > Process Improvement

Process Improvement

RSS Feed Subscribe to this topic  RSS details

110 Items

Sort by Date | Title

Don't "Enron" Your Software Project
By Aaron Erickson
Oct 10, 2009
Aaron Erickson begins a new series on technical finance with a discussion of how technical debt, technical 'off-balance sheet entities,' and technical fraud undermine return on investment.
Robert C. Martin's Clean Code Tip #12: Eliminate Boolean Arguments
By Robert C. Martin
Aug 25, 2009
We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this twelfth tip in the series, the crew learns that Boolean arguments loudly declare that the function does more than one thing. They are confusing and should be eliminated.
Robert C. Martin's Clean Code Tip of the Week #11: Output Arguments are Counterintuitive
By Robert C. Martin
Jul 28, 2009
We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this eleventh tip in the series, the crew learns that if your function must change the state of something, have it change the state of the object it is called on.
Robert C. Martin's Clean Code Tip of the Week #10: Avoid Too Many Arguments
By Robert C. Martin
Jul 6, 2009
We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this tenth tip in the series, the crew learns that functions should have a small number of arguments.
Robert C. Martin's Clean Code Tip of the Week #9: One Step Test
By Robert C. Martin
Jun 12, 2009
We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this ninth tip in the series, the crew learns that being able to run all the unit tests with just one command is imperative.
Robert C. Martin's Clean Code Tip of the Week #8: Your Build Shouldn't Require More Than One Step
By Robert C. Martin
May 16, 2009
We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this eighth tip in the series, the crewmen learn that building a project should be a single trivial operation.
Robert C. Martin's Clean Code Tip of the Week #7: Clean up Old Commented Out Code
By Robert C. Martin
Mar 30, 2009
Robert C. Martin explains why old commented-out code is an abomination.
Robert C. Martin's Clean Code Tip of the Week #6: Avoid Poorly Written Comments
By Robert C. Martin
Feb 27, 2009
We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this sixth tip in the series, the crewmen try to interpret a poorly worded comment.
Robert C. Martin's Clean Code Tip of the Week #5: Avoid Redundant Comments
By Robert C. Martin
Feb 18, 2009
In this fifth tip in the series, the programmers discuss redundant comments, which describes something that adequately describes itself.
Robert C. Martin's Clean Code Tip of the Week #4: Avoid Obsolete Comments
By Robert C. Martin
Feb 11, 2009
A comment that has gotten old, irrelevant, and incorrect is obsolete. Obsolete comments tend to migrate away from the code they once described and become floating islands of irrelevance and misdirection.
Robert C. Martin's Clean Code Tip of the Week #2: The Inverse Scope Law of Function Names
By Robert C. Martin
Jan 21, 2009
The longer the scope of a function, the shorter its name should be.
Robert C. Martin’s Clean Code Tip of the Week #1: An Accidental Doppelgänger in Ruby
By Robert C. Martin
Jan 7, 2009
Robert C. Martin investigates an interesting dilemma: if the implementation of two functions is identical, yet their intent is completely different, is it still duplicate code?
UI Responsiveness: Instantaneous, Immediate, Continuous, Captive
By Steven C. Seow
Dec 8, 2008
When you're coding a website do you take into account how your solution will expend the user’s time?
What Is Clean Code?
By Robert C. Martin
Aug 19, 2008
Robert C. Martin introduces his book, Clean Code, and polls experienced programmers -- including Bjarne Stroustrup, Grady Booch, Dave Thomas, and Ward Cunningham -- on what their definition of "Clean Code" is.
Creating Breakthrough Products Through Collaborative Play: How "Buy a Feature" Works
By Luke Hohmann
Aug 4, 2008
Imrprove the quality of your product features by asking your customers to help you pick them.
The Value of Harmonizing Multiple Improvement Technologies: A Process Improvement Professional’s View
By Jeannine M. Siviy, Pat Kirwan, Lisa Marino, John Morley
Jul 1, 2008
Learn the benefits of a harmonized approach when implementing more than one improvement model, standard, or other technology.
What Is the CMMI Concept?
By Dennis M. Ahern, Aaron Clouse, Richard Turner
May 5, 2008
This chapter is a good introduction to CMMI's scope and usefulness.
The Nature of Software Development
By Scott L. Bain
Mar 7, 2008
In order to be a good software developer, you need to investigate the nature of what you're doing.
Integrating the CMMI and Six Sigma: Strategies
By Jeannine M. Siviy, M. Lynn Penn, Robert W. Stoddard
Feb 8, 2008
Here are some strategic approaches to the joint implementation of the CMMI and Six Sigma.
Using Questions to Design Software Test Plans
By Karen N. Johnson
Jan 11, 2008
Good questions can help you develop ideas and build stronger test plans.

< Prev Page 1 2 3 4 5 Next >