refactoring – Today's Card

Create simpler triggers.

Keep your logic outside of the trigger.

Learn techniques to replace messy software.

Leave it better than when you found it.

Cover your code in unit tests.

There’s no time like the present to make things better.

The code must run all the tests.

Don’t be offended when your code gets refactored.

Chaining a series of methods together can increase dependencies on distant objects.

Two great ideas taste great together, but not in a method.

These can come in handy when refactoring boolean logic.