Has anyone worked with a programmer with a radically different coding style? How do you jive together without wanting to delete and rewrite each others code?
SOLID principle supports good object-oriented design and programming. Five of these principles are described as SOLID: Single responsibility, Open-closed, Liskov substitution, Interface segregation, and Dependency inversion.
The 7 Coding Styles That Are Dated.
Pick one and go with it.
If you are finding it hard to agree, take the time to list pros and cons including:
If you find yourself working with someone too stubborn to change and adapt, well, you have a bigger problem than clashing code style, and dealing with that is out of scope for this question.
If you are the person to adapt your style, avoid the statement "Well if we had chose my way...". If you have agreed on a single style, fully commit to it.
Before getting to this point though, you should probably ask yourself: what are the benefits of having consistent code? You may find that the cost of consistent code (annoying the other developer) is not worth the benefit.
We agree on a standard coding style and enforce it in the form of Visual Studio settings files.
That's a human communication issue. Just talk to each other. Not through code, in person.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With