I don't know about you but when I'm dealing with a technical term, I have an image in my mind's eye of what that thing is. When something doesn't conform to that mental picture I get confused. And, when a term has been used inappropriately, annoyed.
One common word that is misused in IT circles is template. A template is a framework or blueprint that details a common structure. It may be a template for a web page, a word document or perhaps a code class. Whatever. Any resource based on a template will exhibit the common structure defined in that template.
So imagine my confusion when Im trying to get some very poorly documented CMS to work and it refers to a template in the wizard used to configure a content block. So, I'm thinking I've used no template here- its all Created from scratch so I left the field blank.
Guess what? It didn't work. Hours later I find out that the "template" is the base URL of the site. How the hell is that a template? What a stupid term to use for such a thing.
Don't even get me started on roles...
One common word that is misused in IT circles is template. A template is a framework or blueprint that details a common structure. It may be a template for a web page, a word document or perhaps a code class. Whatever. Any resource based on a template will exhibit the common structure defined in that template.
So imagine my confusion when Im trying to get some very poorly documented CMS to work and it refers to a template in the wizard used to configure a content block. So, I'm thinking I've used no template here- its all Created from scratch so I left the field blank.
Guess what? It didn't work. Hours later I find out that the "template" is the base URL of the site. How the hell is that a template? What a stupid term to use for such a thing.
Don't even get me started on roles...
Comment