In my previous post (Productivity for Programmers, #2: Efficient vs. Effective) I gushed about Chad Fowler's book My Job Went to India: And All I Got Was This Lousy Book.
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
globalizationA few highlights from "My job went to India"Sun, 2007/02/25 - 18:00 — mattIn my previous post (Productivity for Programmers, #2: Efficient vs. Effective) I gushed about Chad Fowler's book My Job Went to India: And All I Got Was This Lousy Book Productivity for Programmers, #2: Efficient vs. EffectiveThu, 2007/02/22 - 20:41 — mattBob Walsh and I are writing a series on Productivity for Programmers, which started with his article Productivity for Programmers, #1: Trusted Systems. In it he identified five trusted systems every programmer should have: Tasks, Decisions, Version Control, Code Snippets, and Bugs. I like Bob's break down (no, not the psychological one resulting from writing "Clear Blogging" - different story), so I want to talk about a related characteristic - Efficiency vs. Effectiveness. Efficiency The trusted systems are important, and they are about doing things right, what Drucker called "efficiency" (see David J. Anderson's article Drucker on Effectiveness for a bit more). |
|
||||
| Navigation |