2 added 1 character in body
source | link

Experience has taught me that every team has their own quirks and most of them are best left as-is. It sounds like this manager has few real problems to chew on so this will be their soapbox; so let them keep it; it's important to them.

The end goal of any coding standard is to ease the reuse of the code. Either a coworker or you in the future will have to revisit and figure out what the code is doing and make it do other stuff.

YouYour way looks fine; I don't see a mess, but if everyone built stuff their own way it takes time to spin up and down to each persons style. It's like different authors writing a book. I've been in code that was hard to follow for this very reason.

I have found though that in the long run, the issues that were hard to fix were generally caused by people not doing the big things right, such as hard coding values, improperly using resources, or making an overly complex solution. Simple syntax is very rarely a real issue. I would not worry about it unless this is all the architect seems to worry about. There are bigger issues for them to worry about.

TLTR: I wouldn't sweat it unless this is all they worry about.

Experience has taught me that every team has their own quirks and most of them are best left as-is. It sounds like this manager has few real problems to chew on so this will be their soapbox; so let them keep it; it's important to them.

The end goal of any coding standard is to ease the reuse of the code. Either a coworker or you in the future will have to revisit and figure out what the code is doing and make it do other stuff.

You way looks fine; I don't see a mess, but if everyone built stuff their own way it takes time to spin up and down to each persons style. It's like different authors writing a book. I've been in code that was hard to follow for this very reason.

I have found though that in the long run, the issues that were hard to fix were generally caused by people not doing the big things right, such as hard coding values, improperly using resources, or making an overly complex solution. Simple syntax is very rarely a real issue. I would not worry about it unless this is all the architect seems to worry about. There are bigger issues for them to worry about.

TLTR: I wouldn't sweat it unless this is all they worry about.

Experience has taught me that every team has their own quirks and most of them are best left as-is. It sounds like this manager has few real problems to chew on so this will be their soapbox; so let them keep it; it's important to them.

The end goal of any coding standard is to ease the reuse of the code. Either a coworker or you in the future will have to revisit and figure out what the code is doing and make it do other stuff.

Your way looks fine; I don't see a mess, but if everyone built stuff their own way it takes time to spin up and down to each persons style. It's like different authors writing a book. I've been in code that was hard to follow for this very reason.

I have found though that in the long run, the issues that were hard to fix were generally caused by people not doing the big things right, such as hard coding values, improperly using resources, or making an overly complex solution. Simple syntax is very rarely a real issue. I would not worry about it unless this is all the architect seems to worry about. There are bigger issues for them to worry about.

TLTR: I wouldn't sweat it unless this is all they worry about.

1
source | link

Experience has taught me that every team has their own quirks and most of them are best left as-is. It sounds like this manager has few real problems to chew on so this will be their soapbox; so let them keep it; it's important to them.

The end goal of any coding standard is to ease the reuse of the code. Either a coworker or you in the future will have to revisit and figure out what the code is doing and make it do other stuff.

You way looks fine; I don't see a mess, but if everyone built stuff their own way it takes time to spin up and down to each persons style. It's like different authors writing a book. I've been in code that was hard to follow for this very reason.

I have found though that in the long run, the issues that were hard to fix were generally caused by people not doing the big things right, such as hard coding values, improperly using resources, or making an overly complex solution. Simple syntax is very rarely a real issue. I would not worry about it unless this is all the architect seems to worry about. There are bigger issues for them to worry about.

TLTR: I wouldn't sweat it unless this is all they worry about.