TCR Manifesto

We have reached a point in software engneering profession where we recognize the futility of manipulating computing machinery indirectly. The biggest issue in software engineering/computer programming today is the seemingly inevitable delayed feedback. We make a diff and then have to wait and jump through some hoops until we see the effects of that diff.

This delayed feedback is creating a number of issues, from bugs and defects in the code to bloated and unnecessarily complex ecosystems surrounding the running code.

To remedy this problem, we are embracing TCR (Test-Commit-or-Reset) approach. In a nutshell, we prefer:

• Committing code on every save over committing code after tests pass
• Mutation testing over some arbitrary code coverage
• Hard reset on failing test over testing framework notifying us that test(s) are in red
• Avoid using copy & paste/undo over mechanically copying code