Hi, Vadim Lebedev wrote: > I believe that what you see as amajor drawback is MAJOR ADVANTAGE instead. > This way a person have to try something differrent that he is doing usually > which gives him a chance to learn something new and become better coder. > The important thing that it comes > in small doses so the person does not feel himeself defintively > 'forced'. Everebody is capable to adopt > some different 'accent' for a short moment.
<snip> > With different coding styles the learning process is less dull, which > improves overall efficiency. <snip> > I'd like to hear the opinion of other coders on the list. I'm not yet at your 30 years experience, but I have worked on several projects which have imposed coding standards and several which have been more laxist. In my opinion, what you describe as making work "less dull" just has one conclusion - making source code harder to read. The idea of coding guidelines is not to help the developer who is writing the code, it is to help the developer who is reading the code after the fact. Coding guidelines are not a sufficient condition for having readable code, but they are a necessary condition. If one developer uses 8-space indents with K&R bracing, and another uses 2-space indents with GNU bracing, your project just became twice as hard to maintain. Especially when you're dealing with developers of wide-ranging skills. Your three rules could quite possibly make it into the guide "How to write unmaintainable code". Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
