{
    "href": "/post/2011/09/16/jones-law/",
    "relId": "2011/09/16/jones-law",
    "title": "Jones' Law",
    "author": "pmjones",
    "markup": "html",
    "tags": [
        {
            "href": "/tag/management/",
            "relId": "management",
            "title": "Management",
            "author": null,
            "created": null,
            "updated": [],
            "markup": "markdown"
        },
        {
            "href": "/tag/programming/",
            "relId": "programming",
            "title": "Programming",
            "author": null,
            "created": null,
            "updated": [],
            "markup": "markdown"
        }
    ],
    "created": "2011-09-16 16:54:30 UTC",
    "updated": [
        "2011-09-16 16:54:30 UTC"
    ],
    "html": "<p>While working on my <a href=\"http://daycamp4developers.com/\">Daycamp for Developers</a> presentation, I've been going through some of the \"laws\" related to project management and estimation: <a href=\"http://en.wikipedia.org/wiki/Brooks's_law\">Brooks' Law</a>, <a href=\"http://en.wikipedia.org/wiki/Hofstadter's_law\">Hofstadter's Law</a>, and others.  As part of this, I've decided to coin my own; it's something I've been saying for at least a decade:</p>\n<p><strong>Jones' Law: \"If you plan for the worst, then all surprises are good surprises.\"</strong></p>\n<p>Attend <a href=\"http://daycamp4developers.com/\">Daycamp for Developers</a> and you can hear more about estimating software projects and setting client expectations, as well as lots of other \"soft\" topics that developers can benefit from.</p>\n"
}
