First of all, what are naming conventions? Good question! Our definition first, then we’ll share some wider thoughts on the topic. Naming conventions allow us to apply a pattern and standard to the way we name things within our computer environment. This could be from names of actual files, to folders, to how we store contacts in a CRM (“First name, Last name” or “Last Name, First Name” for example). If we have a standard by which we name things, it makes it easier to search, organise and see at a glance, what things actually are.
According to Wikipedia, “A naming convention is a convention (generally agreed scheme) for naming things. Conventions differ in their intents, which may include to: Allow useful information to be deduced from the names based on regularities.”
Read our full blog post here – https://learningplan.com.au/naming-conventions/
image from Pexels
These are sooo important, even if you’re working alone!
Yeah, this is definitively foundational. My team’s is defined in a Multimedia Style Guide held in configuration management.
I have a personal naming convention for Captivate and it is one of my topics when offering any Captivate training in a company. Everyone has to agree on the accepted naming table, which should take into account the requirements of Captivate to have a unique ID for almost all items, including actions and variables (states are an exception). Moreover, knowing about the filtering possibilities in Captivate and the limited real estate in some dropdown lists, have to be taken into account as well, combined with the normal workflows in the company.
You must be logged in to post a comment.
