{
    "href": "/post/2016/12/12/the-iron-law-of-open-source-bureaucracy/",
    "relId": "2016/12/12/the-iron-law-of-open-source-bureaucracy",
    "title": "The Iron Law of (Open Source) Bureaucracy",
    "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": "2016-12-12 16:09:23 UTC",
    "updated": [
        "2016-12-12 16:09:23 UTC"
    ],
    "html": "<p>Something to watch out for in open-source projects: <a href=\"http://www.jerrypournelle.com/reports/jerryp/iron.html\">Pournelle's \"Iron Law of Bureaucracy.\"</a> In the organization around your project, you will find two kinds of people:</p>\n<ol>\n<li>Those who concentrate on the <strong>goals</strong> of the organization. These are generally coders, devops, and infrastructure folks.</li>\n<li>Those who concentrate on <strong>the organization itself.</strong> These are generally managers of people within the organization, and controllers of how &amp; when the organization communicates within itself and outside itself.</li>\n</ol>\n<p>Pournelle's Iron Law asserts that group 2 will always end up in control of the organization.</p>\n<p>Police your membership accordingly.</p>\n<p class=\"reddit-links\">Read the Reddit discussion about this post <a href=\"https://www.reddit.com/r/PHP/comments/5hxemn/the_iron_law_of_open_source_bureaucracy/\">here</a>.</p>\n"
}