6

Matt's answer gives good advice (as well as Robert Harvey's comments to the question), but both are IMHO incomplete in regards to the question on how to get up to 50 people on board. The organizational issues for trying to get 5 persons working on the same standard are quite different from the issues you face when you have 50 people to manage. About 20 ...


6

Use one or more published coding standards documents as a starting point for discussion. Many large organizations have made their standards documents freely available on the web for just about every conceivable language and framework. Download some of those documents and distribute them for the team to review and consider, making it clear that the documents ...


2

Conflicts arise when people's abmitions clash. You can avoid this by using automated system which enforces conventions. Policy documents and coding guides are of little help because they are subject to interpretation. Commit hook checking formatting rules, naming conventions etc is much cleaner solution which ensures everybody gets similar treatment.


2

I have done this for years myself. I guess you need to follow the same rules you would normally do in any local job. In addition here are few points to consider: Understand that each country has its own style and pace in doing business. In some countries to get a connection to the internet may take few days. Also, sometimes people are not eager to learn or ...


1

I spent several years in the insurance industry in the US. So, I'm familiar with the space. It sounds like what you are talking about is a system that would allow brokers to create proposals that are then handed off to back-office staff for underwriting. If so, I've written a system very similar to that. In the system my team built, there were quotes and ...


Only top voted, non community-wiki answers of a minimum length are eligible