{"id":26,"date":"2008-08-07T16:51:42","date_gmt":"2008-08-07T23:51:42","guid":{"rendered":"http:\/\/blog.bradbushnell.com\/?p=26"},"modified":"2008-08-07T16:51:42","modified_gmt":"2008-08-07T23:51:42","slug":"whatch-where-you-p-opensorce-branding-part-2","status":"publish","type":"post","link":"https:\/\/www.bradbushnell.com\/?p=26","title":{"rendered":"Watch where you &#8216;P&#8217; &#8212; OpenSorce Branding \u2013 Part 2"},"content":{"rendered":"<p>I have already commented on the power of snappy acronyms to aid in marketing an idea. \u00a0But like anything, be careful what you start because if OpenSource has taught us anything, having the freedom to go wherever the wind takes you may leave you explaining to everyone on how the boat ended up at SKULL Island. \u00a0I am not saying that you are going to be left to struggle with an 80 foot gorilla who goes by the name of Kong but let&#8217;s just say that after you fight through the ensuing confusion you might feel like you have. \u00a0What do I mean? \u00a0Take the usage of the word LAMP. \u00a0L . . . hmm for Linux. \u00a0Everyone agrees. \u00a0A . . . .Apache; M. . . . . . MySql; \u00a0P. . . . hmmmm. . . is that for PHP? \u00a0No . . . wait Perl. . . no wait Python? \u00a0The confusion begins to take hold. \u00a0There is an answer which makes sense and it goes like this. \u00a0When the term LAMP was first coined the &#8216;P&#8217; was unequivocally for PHP. \u00a0However, over time people with different skills, tastes, and dispositions began to use the term to speak for what they were currently doing. \u00a0Only, the &#8216;P&#8217; was no longer for PHP. \u00a0It was for Perl or Python. \u00a0Pick your favorite scripting language that begins with a &#8216;P&#8217; and you can call yourself a LAMP developer. \u00a0Am I overstating this a bit . . . a little. \u00a0 However, imagine the frustration when a LAMP developer walks through your door and he doesn&#8217;t know a lick of PHP code. \u00a0These problems can compound themselves. \u00a0Take for example the whole snafu known as JavaScript. \u00a0The story is classic and the <a href=\"http:\/\/www.oreillynet.com\/pub\/a\/javascript\/2001\/04\/06\/js_history.html\" target=\"_blank\">public record<\/a> has more then documented the impact and resulting confusion of this failed nomenclature. \u00a0Ironncially, just when you thought it was dead and buried and we had acknowledged the importance and difference of ECMAScript from Java along comes \u00a0Asynchronous Javascript And XML: \u00a0AJAX. \u00a0 \u00a0I have actually heard people suggest that &#8216;J&#8217; stands for Java. \u00a0Ahhhh, no. \u00a0But why is this? \u00a0Ironically, it&#8217;s the legacy of that first sin committed so long ago and now it&#8217;s polluting everyone&#8217;s attempt at communicating about a new set of technologies and skills. \u00a0This irony continues in that the very terms that you use to be hip, cool, and in-the-know have now in fact cost you time and energy. \u00a0The LAMP developer you have just brought in to interview has no concept of the PHP code fragment you just put in front of him. \u00a0For him, the &#8216;P&#8217; stands for &#8216;Perl&#8217; and he is now looking at you as if you have just offended him. \u00a0So the next time you slough off an acronym and don&#8217;t bother to get it right. . . remember this post. \u00a0Presumably time is money and every day these types of confusions cost organizations lost productivity which translates to the bottom line: \u00a0longer to build the right team, longer to deliver, and more costly to innovate because the right resources are not there to deliver the goods.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I have already commented on the power of snappy acronyms to aid in marketing an idea. \u00a0But like anything, be careful what you start because if OpenSource has taught us anything, having the freedom to go wherever the wind takes you may leave you explaining to everyone on how the boat ended up at SKULL [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,13,12],"tags":[],"class_list":{"0":"post-26","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-opensource","7":"category-staffing","8":"category-technology","9":"czr-hentry"},"_links":{"self":[{"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=\/wp\/v2\/posts\/26","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=26"}],"version-history":[{"count":0,"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=\/wp\/v2\/posts\/26\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=26"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=26"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bradbushnell.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=26"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}