3 ms·
And this depends on who "owns" it. If you don't have communal ownership of code, don't make drastic changes without consultation. This is like rearranging someo
by Jtsummers 8y ago
And this depends on who "owns" it. If you don't have communal ownership of code, don't make drastic changes without consultation. This is like rearranging someone's kitchen for them "because it's more efficient". It's not, because now they don't know their code anymore (I had this happen to me a few times, I know it needed work but the work done made it harder for me to make other changes later that the "helper" didn't know was planned).
If you'll be the one owning the code, do what you want. If it's not yours, check first.
If you do have communal ownership, coordinate and establish style guides, ideally using tools to establish conformance (rather than eye-balling it, this also leads to greater consistency).
- transpy 8y ago> This is like rearranging someone's kitchen for them "because it's more efficient" This randomly reminded me of the time I let my friend use my laptop, only to find out the next morning that he had changed all the colors and styles of my windows xp with a gimmicky "mac skin". So infuriating.
- gwbas1c 8y agoThat's why a team should have code reviews; and everyone should keep an eye on what's changing. This way if someone decides to rearrange something, the stakeholders can hold up the review until they're happy. I've certainly blocked code reviews because of planned changes. That being said, you only "own" code if you own the business. If you think you "own" code, you might need to re-evaluate your ego.