“…For example, a new IDE that reduces compile/debug/edit turnaround is optimizing the wrong problem. Programmers whose time is dominated by the compile/debug/edit cycle are using inefficient work practices—they need to use practices that reduce the number of defects before they reach the compiler. By the time you reach the debugger, the battle for productivity may have already been lost.” A truly excellent article that includes very good suggestions for Effective Work Practices. Even if you don’t read the whole article, I hope you will read the Using Effective Work Practices section.
via John Rodriquez, COP2800 student.