Home > Articles > Process Improvement

Process Improvement

22 Items

Sort by Date | Title

Introduction to the Art of Scalability
Jun 26, 2015
Michael T. Fisher and Martin L. Abbott introduce their book, The Art of Scalability: Scalable Web Architecture, Processes, and Organizations for the Modern Enterprise, 2nd Edition, which covers everything you need to know to smoothly scale products and services for any requirement.
What Went Wrong with Healthcare.gov and How Can It Be Fixed? A Suggested Reading List for Managers and Developers
Oct 31, 2013
Most software projects aren’t as complex as the ACA website, Healthcare.gov, but any software project can benefit from smart project management and development. Jess Johnson takes a look at some books about running a software project and recovering from failure, plus some specific guides for front-end optimization, scalability, security, testing, and refactoring to see how that advice can be applied to healthcare.gov.
The Clean Coder: Saying Yes
May 31, 2011
Professionals are not required to say yes to everything that is asked of them. However, they should work hard to find creative ways to make “yes” possible. When professionals say yes, they use the language of commitment so that there is no doubt about what they’ve promised.
Robert C. Martin's Clean Code Tip #12: Eliminate Boolean Arguments
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
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
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
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
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
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
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
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
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
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?
What Is Clean Code?
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.
Introduction to Process Control and Instrumentation
Apr 18, 2003
Welcome to the world of process control and instrumentation! Discover how to identify and classify possible control objects and variables, assess the importance of process control, sketch a process instrumentation, and much more.
Test Driven Development: Equality for All
Jan 24, 2003
Kent Beck discusses how to achieve equality using Value Objects, Dollars, and Triangulation.
Quality By Design, Part 1: Avoiding Rotten Code
May 31, 2002
We all have to face the fact that some software stinks; it doesn't work right or it just plain feels wrong. Fixing these problems is simple, but may not be easy. We have to understand the nature of software development and make sure that we allow ourselves enough time to do a good job.
Is Software Engineering a Good Choice for Your Product?
Feb 8, 2002
In order to understand whether or not software engineering is for you, read Pete McBreen's introduction to software engineering from his book, Software Craftsmanship — his answers might surprise you.
Software Development: Dismantling the Waterfall
Feb 8, 2002
Of all the ways of approaching the software development lifecycle, the waterfall is probably the worst. So why does it continue to dominate our thinking? Simple: We have failed to let everyone know how software development really works.

Page 1 2 Next >