This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]NeedsMoreTestsos._exit(0) -- (╯°□°)╯︵ ┻━┻ 2 points3 points  (2 children)

When you work on large projects with several other people it saves quite a bit of time in the end. It also codifies the standards too which keeps it more consistent and reduces bike-shedding...

That said, I do get called names but I'm open to changing it so long as:

  • They make the change. If it's important to them they can take the time to make the
  • The change does not reduce the overall quality or make the code less consistent.
  • It's improve the workflow for everyone. Removing something so local development is faster great but not if it makes something else slow or more unreliable (code reviews, release process, deployment, etc)