{"id":1498,"date":"2012-01-13T15:32:10","date_gmt":"2012-01-13T22:32:10","guid":{"rendered":"http:\/\/162.243.68.163\/blog\/?p=1498"},"modified":"2012-08-07T11:11:53","modified_gmt":"2012-08-07T17:11:53","slug":"totally-gay-blog-post","status":"publish","type":"post","link":"https:\/\/tekhedd.com\/?p=1498","title":{"rendered":"Totally gay blog post"},"content":{"rendered":"<p>Sometimes, the word <em>stupid<\/em> is not enough. Today I learned some of the terminology used to describe parts of <a href=\"http:\/\/agilemanifesto.org\/\">Agile software development<\/a>. Agile is a popular &#8220;methodology&#8221; adopted by software companies as an alternative to admitting that they are incapable of putting together a development process that works. It is essentially the same as having no process whatsoever, but with the subtle difference that your CEO can tell investors and large customers that you &#8220;have a process.&#8221; And he&#8217;ll be taken seriously.<\/p>\n<h3>Agile: a flowery way to say Out Of Control<\/h3>\n<p>Agile allows developers to maintain the illusion of software process, while allowing developers to do whatever they want with no process or plan. How? Agile accomplishes this through the use of Flowery Terms. Each step in software development at a company with no process is documented and given a Flowery Name.<\/p>\n<p>For example, when collecting product requirements, a developer who follows a process would normally document Use Cases. Agile&#8217;s Flowery Name for this is\u00c2\u00a0 &#8220;User Stories.&#8221; I am not making this up! And the important difference between Use Cases and User Stories is that with Agile you are encouraged to be half-assed and never finish them. Well, officially, you are encouraged to do &#8220;just enough&#8221; and come back and &#8220;finish them later,&#8221; but we all know that this never happens. With Agile, we do things just like we always have in the past, except that now it&#8217;s our process, and it has an investor-friendly name.<\/p>\n<p>So I guess I&#8217;ve always been Agile. And here I thought that we were &#8220;winging it&#8221; at some of those companies!<\/p>\n<h3>Surely there is a better way to say this<\/h3>\n<p>But enough about Agile. Where I work, we have processes and we follow them. They are not overly burdensome and we get a lot of work done. I&#8217;ll be damned before I use the name &#8220;User Stories&#8221; to describe how we define requirements. That term is completely, it&#8217;s totally&#8230; something.<\/p>\n<p>I can only describe &#8220;User Stories&#8221; in one way: that name is Totally Gay. And now I have a problem. Because I&#8217;m not a homophobe&#8211;but I feel about &#8220;User Stories&#8221; the same way a homophobe feels about gays. Isn&#8217;t there a non-bigoted word that means the same thing? &#8220;Stupid&#8221; is not a good substitute&#8211;it isn&#8217;t even part of my definition. Another word that implies all these things at once:<\/p>\n<ul>\n<li>lame<\/li>\n<li>laughable<\/li>\n<li>contemptible, even<\/li>\n<li>slightly offensive<\/li>\n<\/ul>\n<p>The phrase &#8220;laughably lame&#8221; works, but &#8220;laughably&#8221; is intellectual and &#8220;lame&#8221; is anti-intellectual, resulting in a phrase that nobody will use and is hard to say.<\/p>\n<p>I want a simple phrase that means the same thing as &#8220;totally gay&#8221;, but which doesn&#8217;t imply that I&#8217;m a complete douche. (If you use the phrase &#8220;totally gay&#8221; without apologizing, you are a douche.) Google turns up nothing.<\/p>\n<h3>I&#8217;m wasting your time<\/h3>\n<p>This should all be unnecessary. This whole blog post would fit in one Tweet if I could just say &#8220;Agile software development is totally gay&#8221; in a way that wasn&#8217;t, you know, totally gay&#8230;or something.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Sometimes, the word stupid is not enough. Today I learned some of the terminology used to describe parts of Agile software development. Agile is a popular &#8220;methodology&#8221; adopted by software companies as an alternative to admitting that they are incapable of putting together a development process that works. It is essentially the same as having [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[246,249,245,251,248,247,250],"class_list":["post-1498","post","type-post","status-publish","format-standard","hentry","category-other","tag-agile","tag-flowery-name","tag-gay","tag-lame","tag-process","tag-software","tag-stupid"],"_links":{"self":[{"href":"https:\/\/tekhedd.com\/index.php?rest_route=\/wp\/v2\/posts\/1498","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tekhedd.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tekhedd.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tekhedd.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/tekhedd.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1498"}],"version-history":[{"count":8,"href":"https:\/\/tekhedd.com\/index.php?rest_route=\/wp\/v2\/posts\/1498\/revisions"}],"predecessor-version":[{"id":1696,"href":"https:\/\/tekhedd.com\/index.php?rest_route=\/wp\/v2\/posts\/1498\/revisions\/1696"}],"wp:attachment":[{"href":"https:\/\/tekhedd.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1498"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tekhedd.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1498"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tekhedd.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1498"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}