Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RailsConf 2019 - From test && commit || revert to LIMBO by Shane Becker _______________________________________________________________________________________________ Cloud 66 - Pain Free Rails Deployments Cloud 66 for Rails acts like your in-house DevOps team to build, deploy and maintain your Rails applications on any cloud or server. Get $100 Cloud 66 Free Credits with the code: RailsConf-19 ($100 Cloud 66 Free Credits, for the new user only, valid till 31st December 2019) Link to the website: https://cloud66.com/rails?utm_source=-&utm_medium=-&utm_campaign=RailsConf19 Link to sign up: https://app.cloud66.com/users/sign_in?utm_source=-&utm_medium=-&utm_campaign=RailsConf19 _______________________________________________________________________________________________ Kent Beck (TDD, eXtreme Programming, Agile Manifesto) has a couple new ideas. They both sound so terrible and impossible that they just might be totally amazing. 1. test && commit || revert If tests pass, commit everything. If they fail, revert everything. Automatically. Wild. 2. LIMBO. Anything that's committed is pushed. Anything that's committed by teammates is automatically pulled in while you work. So wild. Does this work? Does it scale? Will I always be losing important progress because of a typo? Will this make me a better / faster / happier programmer? We'll cover tools, process, deficiencies, mental models, and experiences. Show up and see what happens.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In this talk from RailsConf 2019, Shane Becker discusses the concept of "Test && Commit || Revert" (TCR), exploring its origins, practical applications, and implications for software development. The talk is structured in three parts, starting with a technical overview of TCR, followed by a historical context that highlights the evolution of programming patterns and methodologies that led to TCR, and concluding with practical insights from Becker's own experiences implementing the concept. ### Key Points Discussed: - **Understanding TCR**: TCR is a process where if tests pass, all changes are committed; if they fail, all changes are reverted. This mechanism emphasizes rapid feedback and encourages programmers to work in small increments. - **Historical Context**: Becker shares a brief history of influential concepts and figures in software development, such as Kent Beck, who contributed to Test-Driven Development (TDD) and the Agile Manifesto. The principles of TCR can be traced back to architectural patterns discussed in books like "A Pattern Language". - **The Evolution of Programming**: The talk reflects on how the TCR methodology is grounded in past programming practices and philosophies, asserting that many modern practices are derived from earlier ideas. - **Implementation and Lessons Learned**: Becker recounts practical experiences using TCR, identifying challenges such as reverts during coding sessions, which led to valuable lessons. Important takeaways include the significance of fast tests, the benefit of making small, incremental changes, and trusting the automation process. - **Practical Application**: He encourages attendees to implement TCR in real-world projects, emphasizing experimentation with TCR while remaining in a safe coding environment. Becker offers suggestions for improving tool integration and enhancing TCR practices. ### Conclusions and Takeaways: - Becker asserts that TCR can potentially reshape the way programmers approach software development. It fosters a culture of safety in experimenting with code, while boosting efficiency and reducing the fear of failure in committing code changes. - The talk concludes with a call to action for developers to explore TCR, whether in toy projects or live applications, and to engage with the broader programming community about their experiences with this approach. Overall, Shane Becker's presentation at RailsConf 2019 sheds light on an innovative approach to coding practices that combines history, theory, and practical application in a rapidly evolving field.
Suggest modifications
Cancel