Perhaps not as well. If people are following the coding standards for the organization then the code for the most part looks far more similar.
When I am working with a development team, I will tend to adjust my unique style to better match what everyone else is doing. Even if it means doing coding methods that I will normally disagree with.
If the code tends to use a bunch of Goto's instead of Procedures or classes. I will use those GOTO not for my benefit, but for people who will maintain my code later on, so they won't have to change their mindset and debugging strategies to see what the program is doing to do future corrections.
I will go full Object Oriented if the group of people that I am working with do their coding full OO.
My personal style would be more procedural, than OO. Not due to lack of knowledge or not realizing OO advantages and disadvantages. But if I am to code on my own, I code in the way that My Mind handles the requirements, and how I feel would be easier for me to change and fix my code in the future.
I think this method is best for ID based on personal code, vs group corporate code, where a lot of your particular style is hidden.