
|
|
Iron Fist of Naming Conventions |
|
|
Saturday, 01 July 2006 |
|
Page 2 of 2 Automated Enforcement vs. Social Pressure
Once you can get a team to agree on naming conventions, then the next question that comes up is how to enforce those conventions.
Some level of technical enforcement is typically the initial approach.
- Write all your scripts so they name files and directories correctly.
- Have scripts stop processing or “error out” if files or directories aren’t named as expected.
- Create scripts that build placeholder structures for your assets, complete with correctly named files.
- Have your asset management tools enforce naming during the importing of files and directories.The other common approach is via social engineering.
- New user training.
- Ongoing production training.
- Peer guilt.
Where do I stand? I am always in favor of technical enforcement when it makes sense. Technical enforcement should serve to remind people of the correct conventions. It can, however, get to be fairly complex to manage. I would suggest putting your logic for naming conventions into a common library or module. All tools can then leverage this common code. Additionally, writing code to enforce your conventions is the best way to understand the complexity of your conventions.I feel that in the long run social engineering will give more lasting results, especially if the studio takes training seriously. Productions really shine when they have a strong training program. New users are more productive faster and understand the production processes more completely when they get good training. Naming conventions (along with asset organization) should be the cornerstone of any production training curriculum. With ongoing training all users will know what the conventions are and why they are important.When used in conjunction with technical enforcement and training, peer guilt can easily get you 99.9% compliance with naming conventions. There is no better reminder than having your cubemate turn around, tap you on the shoulder, and point out how your misnamed file broke her automated processing script!
So Get To It!
You should now have enough ammo to go to your manager and request the time and resources to help get a naming convention in place. The time you save during production will greatly outweigh the time you spend getting a convention up and running. Time is money to a production. Nothing makes a producer’s eyes light up like saying “We are ahead of schedule!” And you will have your naming convention to thank.
--kevin
Editorial support from Steve Carter, Marlon Montgomery and Courtland Townsend.
Mind The Gap works with animation studios around the globe to improve production efficiency by helping them with the design, implementation, and optimization of the production pipeline and workflow. Mind The Gap also offers world-class training and workshops on the best practices of production to studios, educational institutions, and artists so they can remain truly competitive.
For more information visit http://www.animationpipeline.com or email
This email address is being protected from spam bots, you need Javascript enabled to view it
|
|
|
|
|
|

|

|
This website is optimized for Firefox!
(C) 1996-2006 Toonstruck, LLC CGCHAR is maintained by Rick May
|

|