No, mostly not. Doing my job properly gives me job security for the most part - but this is one of the things where I don't see any benefit for yourself, there is only a benefit for your employer. Of course, I'm not advocating writing cryptic undocumented obfuscated mess (that's just plain unethical, even if it's "good" for you), but coding in a "standard" style just benefits your employer, not you. It just means you are more easily replaceable without any benefit for you. You won't learn more from doing it, you won't gain any skills or anything.
> It just means you are more easily replaceable without any benefit for you
What does this even mean?
Companies don’t (well, shouldn’t) hire developers to just write code. They hire them to solve problems. I’m not going to more easily replaced because my code follows the same styles as others, if I am the one solving the problems they have.
Yes, but others can also solve those problems. And if you make your code really standards-comforming, management will see that they could onboard another programmer really quickly. This is what you want to avoid.
Not to be mean or rude, but if we had a developer that was refusing to adhere to our standards, they not last long. Being able to produce code in agreed upon standards is table stakes.
You would not last long in my team. When you “forget” the standard, you would have to rewrite your code. In the end you would perform a lot worse than other team members.
Anyone should be able to follow coding standards, you do not have to be smart for that. You just have to be able to put aside your ego and follow what the team is doing. I am a lot more forgiving to people making mistakes than to people forgetting the coding style.
And anyhow, I enforce the code style by making sure the code simply does not build if you do not follow it.
