Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Fluency is "what you can say without having to think about how to say it." "Refactoring" is a language that describes ways to make your code better. I want to inspire you to learn more of that language, so you can make your code better without having to think about it. I'll walk you through the process of reworking a 50-line controller action that's hard to comprehend, let alone refactor. We'll tease apart fiendishly intertwined structures, embrace duplication, use dirty tricks to our advantage, and uncover responsibilities—and bugs!—that weren't obvious at first glance. Help us caption & translate this video! http://amara.org/v/FG8j/
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 the talk 'Fluent Refactoring' presented by Sam Livingston-Gray at the LoneStarRuby Conf 2013, the focus is on enhancing coding skills through the practice of refactoring. Refactoring is described as a disciplined technique for restructuring existing code without altering its external behavior, likened to a language that can help make code better and more understandable. Livingston-Gray draws parallels between math and programming, presenting fluency in programming as similar to fluency in a language where the aim is to express ideas without overthinking the syntax. Key points discussed include: - Definition of fluency in programming as the ability to write code effortlessly under stress, similar to fluency in spoken language. - The importance of understanding refactoring as structured techniques that improve code clarity without changing what the code does. - An anecdote about working with complex code in a Rails application emphasizes the challenges developers face with tangled and unreadable code. - A demonstration of refactoring a complicated controller action illustrates the process of breaking down a large method into smaller, more manageable parts, extracting duplicate code, and restructuring code for better readability. - The principles of Single Responsibility and the importance of good naming conventions in improving code quality were highlighted as crucial methods in refactoring. Livingston-Gray concludes by encouraging developers to practice refactoring regularly and experiment with different structures and approaches. He insists that consistently applying these methods leads to greater fluency and can significantly enhance the developer's ability to manage complexity in their code. Overall, the talk reinforces the relevance of systematic refactoring skills that transcend just language syntax, illustrating that fluency and clarity in programming can be achieved through disciplined practice and thoughtful application of techniques.
Suggest modifications
Cancel
