Do you manage programmers or software engineers, people who write code for a living? If you do, check out Paul Graham
's Holding a Program in One's Head
. It explains the importance of getting a program into a programmer's working memory ("head") and the damage to results and productivity that can be created by distractions. I think the same applies to certain other fields, too. I know that modeling and simulation work quite resembles programming in that regard; perhaps you can list other fields where it takes significant time to get all the pertinent information into our heads before we start real work.
As an aside, Graham recommends succinct languages for more powerful results. J
is one language that's quite succinct and quite powerful. It's easy for many of us to use as aids in our current work; that's why I recommend it for managers and knowledge workers
, not because we're dense but because our primary contribution isn't programming, and I find J augments my capability
without making me a programmer. I also recommend J for serious programming work, for I've seen what true J experts can do
, and it's both impressive and leverageable.
Labels: management, productivity