There is a natural inflection point the moment developers commence their work. The fuzziness of the business world must, one way or another, be resolved into code. Telling developers to \u2018be flexible\u2019, \u2018remain open-minded\u2019 or \u2018embrace change\u2019 is not very helpful. Unfortunately, that\u2019s precisely how some business folk and managers speak to the technical team.<\/p>\n\n\n\n
\u2018Here\u2019s my grand vision; I don\u2019t know the specifics; you figure them out, but don\u2019t take too long (because we have an arbitrary deadline)\u2019<\/em>. Yet, in reality, the compiler is a very unforgiving taskmaster and demands to know every little detail. Should it be a variable-length Unicode string or a fixed array of Ascii characters? Can it be modified after initialisation and should it go on the stack or the heap?<\/p>\n\n\n\n Most clients don\u2019t know or care about this level of detail, but that doesn\u2019t mean it\u2019s unimportant. What if the business wants to launch in a new region? Then localisation and choice of string become front of mind. Hopefully, the requirements surfaced this future need. How about low-latency transfers and fast processing at the receiver? Different considerations then become important.<\/p>\n\n\n\n It wouldn\u2019t be reasonable to expect non-technical folk to really understand every technical decision the developers must make, but equally, it\u2019s not reasonable to be ignorant and yet demand faster delivery without considering what gets sacrificed in doing so. Anyone can confidently use the term \u2018API\u2019 in a conversation, but it doesn\u2019t mean they know what it is, or how it works. Don\u2019t be that executive or manager.<\/p>\n","protected":false},"excerpt":{"rendered":" There is a natural inflection point the moment developers commence their work. The fuzziness of the business world must, one way or another, be resolved into code. Telling developers to \u2018be flexible\u2019, \u2018remain open-minded\u2019 or \u2018embrace change\u2019 is not very helpful. Unfortunately, that\u2019s precisely how some business folk and managers speak to the technical team. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[],"class_list":["post-452","post","type-post","status-publish","format-standard","hentry","category-software-development","missing-thumbnail"],"_links":{"self":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/452","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/comments?post=452"}],"version-history":[{"count":1,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/452\/revisions"}],"predecessor-version":[{"id":453,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/posts\/452\/revisions\/453"}],"wp:attachment":[{"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/media?parent=452"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/categories?post=452"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/localhost:8082\/wp-json\/wp\/v2\/tags?post=452"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}