Pure Danger TechAlex Miller’s technical blog

1. Mike Kaufman Jul 11 2007 / 3pm

   Wonderful ! But I know I read lots of docs/specs at least (and usually groan about how incomplete and ambiguous they are). You clearly do too. So maybe it should be “No one ELSE reads anything”…
2. Jay Meyer Jul 11 2007 / 9pm

   good observation. When being whipped by business to make it cheap and fast, we don’t have time to do it well. Words make the software neither cheaper nor reach the deadline faster, so who needs them?
3. It’s Just a Bunch of Stuff That Happens » Blog Archive » What is the Miller Principle? Jul 11 2007 / 9pm

   […] I only made it through the first sentence of The Miller Principle before I stopped reading. I can only guess what he’s talking about…whatever it is, it’s probably good. […]
4. M Easter Jul 12 2007 / 3am

   I would add: code comments and any email longer than one line!

   ;-)
5. Bob Jul 12 2007 / 6am

   Nice principle but do you have any examples of things this principle might apply to?

   You should write some more principles too!
6. links for 2007-07-13 « betaalfa Jul 12 2007 / 10pm

   […] Pure Danger Tech » Blog Archive » The Miller Principle (tags: miller principle) […]
7. Alex Jul 13 2007 / 6am

   I can only assume these comments were really funny as I didn’t really get around to reading them.
8. Erik Engbrecht Jul 13 2007 / 4pm

   I think this is only true with poorly written things. I’ve written specs that were not only read, but remembered years later and requested for specific content.

   You just have to do a good job writing it.
9. Alex Jul 13 2007 / 8pm

   @Erik: Actually, I think it’s fairly pervasive even for well written documents. But of course, good writing is more likely to be read.
10. Patrick Forhan Jul 16 2007 / 11am

    Yep. And never ask more than one question in an email, too. Only one will be answered.
11. Pure Danger Tech » Blog Archive » Patterns I Love/Hate #3: Visitor Jul 17 2007 / 12am

    […] The Miller Principle […]
12. dave Jul 17 2007 / 3am

    What is the miller principle ?
13. Kishore Senji Jul 31 2007 / 1am

    The last two entries are funny and sadly true more often than not.
14. Nathan Aug 18 2007 / 10pm

    hi i enjoyed the read
15. Alex dP Aug 21 2007 / 2am

    According to Steve McConnell’s excellent book “Code Complete”, good code equals readable code. So, good code doesn’t need comments anymore. By the way, code is not all. So, I don’t agree with you on some points. If many consultants are paid by the massive paper weight they produce, in the other hand, effective documentation exists. It just needs to be well distilled with a constant goal : communicate only the good information.
16. Alex Miller - Nuke your inbox Aug 24 2007 / 9am

    […] Personally, I’m not willing to go quite this far, but I appreciate the sentiment. It certainly resonates well with the Miller Principle. […]

All content © 2005-2008 by Alex Miller

Entries RSS Comments RSS Java 7 RSS Music RSS