Coding as a Team: What I Call Uniformed Coding

What Is Uniformed Coding?

Think of it as an Interface, the contract between members of your team. 

You define the way you code, create a structure which everyone follows.

Why Use It?

By having a contract between members of your team you can ensure consistent code.

I'm not referring to the use of the single framework or library but in effect creating an interface from which everyone follows. 

No matter what frame or programming language the project is written in you as a member of the team should be able to know where to find a particular type of method.

For example, I would create a set of method which every member in my team must apply to their classes or objects. Lets say one of the methods is called 'build', now I define that this function will be responsible for building/creating the Class, elements within a Class or an object.

So now that I have enforce Uniformed coding, every time I need to amend a project to remove/add elements all I have to do is go to the 'build' method and that should be where the code is. 

Imagine a much advanced Interface, by using Uniformed coding not matter what programming language the code is written in you will be able to understand it.

Remember that all the projects become consistent without being tide down to a framework which might get out date in the near future. 

Example of My Uniformed Coding Interface:

• build(): creation of all the parts of the element.
• setStyle(): styling of  all the parts of the element.
• arrange(): the positions/sizes of all the parts of the element.
• purge(): destroying and purging of the Class.
• show(): to show Class.
• hide(): to hide the Class.

As you can see, you can apply this Interface to any programming language.