Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
"Welcome! We're so excited to have you 🤗 please excuse the mess." – if a codebase could talk When we join a new team or start a new project, we have to onboard to the codebase. Diving into code that we're unfamiliar with can be stressful or make us feel like we don't know what we're doing. And the longer the codebase has been around, the more intense those feelings can be. But there are steps we can take to understand new code and start contributing quickly. In this talk, we'll cover how to build our code comprehension skills and how to make our own code welcoming to guests in the future.
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 "Come on in! Making yourself at home in a new codebase" at RailsConf 2022, Mercedes Bernard addresses the common anxieties developers face when onboarding to new codebases. The primary theme revolves around strategies to facilitate a smoother entry into unfamiliar coding environments, likening the experience to settling into a new home. Below are the key points discussed in her talk: - **Feeling at Home in Code**: Mercedes emphasizes that joining a new codebase can be likened to entering a new house. Familiarizing oneself with the layout, finding essentials, and understanding the space is crucial for comfort. - **Documentation as Orientation**: The first step in immersing oneself in a codebase is to thoroughly examine the documentation. Checking the README, contribution guidelines, and diagrams serves as a map to navigate through the unfamiliar code. - **Setting Up the Codebase**: Just as one would inspect the amenities of a new place, establishing the development environment gives insight into dependencies and the overall architecture. Mercedes highlights the importance of understanding how everything fits into the larger system. - **Iterative Learning Process**: Rather than striving to learn everything at once, starting with small contributions, such as fixing bugs or implementing features, allows developers to gradually understand the codebase. Scaffolding (breaking information into manageable pieces) and spaced learning (regular practice intervals) enhance this process. - **Version Control Exploration**: Utilizing version control history and pull requests can aid in understanding past efforts and solutions, providing context and direction for new contributions. - **Interactive Debugging as a Tool**: Engaging in interactive debugging helps developers discern the functionality of their code, acting like a guided tour through the intricacies of the codebase. - **Writing Contributions**: When making changes, it is vital to document those contributions clearly for future developers, akin to leaving a welcome note for guests in a home. Clear commit messages, pull requests, and proper tests foster a sense of community and ease for future contributors. - **Maintaining Documentation**: Continuous updates to documentation and diagrams ensure that newcomers are not left in the dark, supporting ease of onboarding for future developers. In conclusion, Mercedes stresses that by fostering a welcoming atmosphere and contributing incrementally, developers can overcome the daunting task of navigating new codebases. With patience and curiosity, we can cultivate comfortable and collaborative coding environments that benefit everyone involved.
Suggest modifications
Cancel
