Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
It's very effective; using Pokemon to catch all code smells When learning new skills, connecting what you already know is key. Studying the most common code smells in Ruby and their fixes, exposes a pattern that is similar to how the game mechanic in the popular video game Pokemon works. Grouping certain types and finding the way to beat them. Melanie Keatley - https://twitter.com/Keatley EuRuKo 2019
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 her talk at Euruko 2019, Melanie Keatley presents a unique approach to understanding code smells through the lens of Pokémon, making the concept more relatable and easier to comprehend. Keatley, who transitioned from journalism to software development, initially faced imposter syndrome but found confidence through learning about code smells—a term for poor practices in code that can lead to problems. The main points discussed include: - **Personal Background**: Keatley shares her journey from journalism to software development, emphasizing the importance of self-acceptance and learning. - **Code Smells**: She introduces the term 'code smells' and explains its significance in writing maintainable code. - **Pokémon Analogy**: Drawing parallels between Pokémon types and code smells, Keatley proposes creating characters for various code smells to better understand them. For example: - *ChatScula* represents excessive comments in the code. - *Speculative Generality* embodies unnecessary future-proofing of code. - *Divergent Change*, illustrated by *Dominiontron*, makes changes to a class more complicated. - **Groups of Code Smells**: Keatley categorizes code smells into groups, such as 'Dispensables' (easily removable code), 'Change Preventers' (hurdles to making changes), and 'Bloaters' (unnecessarily large code structures). - **Benefits of Doodling**: She also discusses research suggesting that doodling, like creating Pokémon characters for code smells, can significantly improve memory recall and creativity, as visuals aid in information processing. - **Actionable Takeaways**: Keatley encourages engineers to engage in visual learning techniques, hinting at the underutilization of doodling in programming discussions. She urges teams to incorporate more visual methods into their workflows for better understanding and communication. In conclusion, Keatley's presentation creatively bridges a childhood favorite with the technical world, allowing developers to tackle code smells more effectively and enjoyably. The session reveals that drawing or doodling can not only aid in memory retention but also foster collaboration and innovation in coding practices.
Suggest modifications
Cancel
