If you are helping someone who's work conforms to a different but consistent and sane style guide, you should be able to adapt to it. Nobody likes to help untangle someone's spaghetti code or deal with assets with names they can't understand. When working within a team or discussing within a community, it is far easier to help and to ask for help when people are consistent. If you see someone working either against a style guide or no style guide, try to correct them.
Friends do not let friends have bad style. This style guide is written with best practices in mind, meaning that by following this style guide you will also minimize hard to track issues. It also allows for more productive creation and maintenance as one does not need to think about style, simply follow instructions. Conforming to a style guide removes unneeded guesswork and ambiguities. Moving from one project to another should not cause a re-learning of style and structure. Rebecca Murphey All structure, assets, and code in any project should look like a single person created it, no matter how many people contributed. There should be a style guide, and you should follow it. Style guides should be living documents however and you should propose style guide changes to an existing style guide as well as this guide if you feel the change benefits all usages. Any inconsistency between an existing style guide and this guide should defer to the existing.
If you are working on a project or with a team that has a pre-existing style guide, it should be respected. This article contains ideas for setting up a projects structure and a naming convention for scripts and assets in Unity.ġ.1 Style If your project already has a style guide, you should follow it.
0 kommentar(er)
