Perfection – or good enough.

Every month or so someone tells me my work is too detailed, or that I am a perfectionist.  Ironically every week or so someone also tells me that I have not covered some topic or other in sufficient detail.  However the, “its too detailed”, or “too complex”, audience tends to be the one that pays the bills so they are more important to listen to.  I came across this nice little post on the subject, and I have extracted a snip from it here:

One important lesson I’ve learned about designing software is that sometimes it pays to smother one’s perfectionist engineer instincts and be less ambitious about the problems one is trying to solve. Put more succintly, a technology doesn’t have to solve every problem just enough problems to be useful. Two examples come to mind which hammered this home to me; Tim Berners-Lee’s World Wide Web and collaborative filtering which sites like Amazon use.

However I am not a person who likes to compromise so I am gradually working towards a way of solving this problem, and its pretty simple and obvious.  Stop writing documents and start writing web sites.  This post is an example, (although not a very good one), short and direct but with links off to more detailed supporting material.