arlobelshee / ArlosCommitNotationLinks
A notation for small commits messages that show the risk involved in each step
☆21Updated last year
Alternatives and similar repositories for ArlosCommitNotation
Users that are interested in ArlosCommitNotation are comparing it to the libraries listed below
Sorting:
- Exercises to practice breaking dependencies to test legacy code.☆18Updated last year
- Fortune-telling for racehorses☆16Updated 3 years ago
- JUnit 5 extension for Kent Beck's test commit revert workflow.☆15Updated this week
- ☆33Updated 6 years ago
- This is a refactoring kata for improving your coding skills☆122Updated 3 months ago
- Printout excerises to learn refactoring☆13Updated 2 years ago
- Everything you need to conduct an introductory workshop on test-driven development.☆135Updated 3 years ago
- ☆12Updated 2 months ago
- exercise for practicing refactoring☆22Updated last year
- Refactoring LCD Numbers to remove the dependency injection framework.☆18Updated 4 years ago
- This page is an attempt to centralize useful resources (code katas, workshops, talks) that can help aspiring Software Craftsperson in the…☆45Updated last week
- This is a poster that acts as a reminder for the rules of Conway's Game of Life. You can hang it to a near wall during a coderetreat (cod…☆44Updated 2 years ago
- TCR (Test && Commit || Revert) utility☆53Updated last week
- Repository hosting the Software Craft And Testing Unconference UK website.☆62Updated last month
- Advent of Craft 2023☆93Updated last year
- A kata about testing bugs in legacy code without 3 weeks of feature freeze. Leveraging on the Mikado Method and the Test Data Builder pat…☆36Updated last year
- ☆30Updated 3 weeks ago
- Code from Michael Feathers presentation about "Tell, Don't Ask" at Craft 2019☆18Updated 6 years ago
- Set up a new machine as a development environment for your project☆32Updated 9 months ago
- A legacy refactor kata, focused on the violation of the tell don't ask principle and anemic domain model☆32Updated 2 years ago
- Refactoring exercise where data layer and business layer are not clearly separated☆19Updated last year
- Legacy Code Retreat - Grenoble 2011☆61Updated last year
- A timer for the "baby steps" exercise/technique for doing TDD☆61Updated 2 months ago
- Identifying & fighting your team’s systemic issues creating your legacy☆74Updated 9 years ago
- Learning hours for Craft / Technical Coaches☆26Updated 2 years ago
- a kata for practicing both testing with Combination Approvals and 'Split Phase' refactoring☆17Updated last year
- AGILE TECHICAL PRACTICES mentoring program☆21Updated 4 months ago
- Turnkey Kata-Bootstraps☆23Updated this week
- An exercise on refactoring☆17Updated 3 years ago
- A Java-based sample application for Batect☆11Updated 2 years ago