Test && commit || revert
summary
Explains and demos TCR using an limited-wip plugin in IntelliJ while coding a Kotlin FizzBuzz demo, claiming the workflow forces very small, safe changes. The tool runs tests before allowing commits, does an automatic commit on pass and an automatic revert on fail, so broken work disappears and stack traces/inline debugging are lost. Shows iterative refactors, copy/paste bug and recovery, discusses commit-message and push options and the tradeoffs between safety and loss of intermediate state.
AI-written summary · about
chapters (4)
- 0:00Introduction to TCR
- 3:23Why use TCR workflow
- 5:10TCR demo with FizzBuzz
- 12:44TCR challenges and recap
related talks
50mLimited work-in-progress for developers
08mtest && commit || revert. What?!
35mQuickly and Safely Refactoring Legacy Code
45mTDD makes you a better everyday developer
01h 06mBeyond Test Driven Development
40mTesting Legacy Code: Safe Refactoring
01h 03mRewiring your brain with test driven thinking in C++
43mFrom 0% to Cleanly Refactored 100% tested code