Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Are you from a non-C.S. background? What about someone you mentor? Many junior devs' top focus is building technical knowledge. However, they already have other skills that can help them in their roles immediately! Some of these include helping their team focus on the right tasks and working well with stakeholders like PM and support. This talk will discuss the non-technical contributions junior devs can make now and how their senior dev mentors can help them ramp up more quickly as a result. I studied Biology in college and was all set to attend medical school and fulfill my mother's dream of my becoming a doctor. Instead, I got a job at Google in tech support. After five years at Google, I took a sabbatical to attend Hackbright Academy. Now I'm a junior developer at New Relic. Help us caption & translate this video! http://amara.org/v/FG0m/
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 video titled "How to be a Better Junior Developer," Katherine Wu, a junior developer at New Relic, shares insights on navigating the challenges faced by junior developers, particularly those transitioning from non-computer science backgrounds. The talk is structured around two primary challenges: the overwhelming amount of knowledge to learn and understanding how to contribute effectively to a team. Wu emphasizes the value of leveraging non-technical skills to aid in learning and team collaboration. Here are the key points discussed: - **Understanding Challenges**: Wu identifies two main challenges for junior developers: the vast amount of technical learning required and the difficulty in determining how to assist the team. - **Learning Strategies**: - **Get Help**: Build relationships and network within the team. Wu suggests remembering personal details about colleagues to foster connections and to approach other team members respectfully for guidance. - **Make It Easy for Others to Help**: Clearly articulate your current understanding and specific areas of confusion when seeking assistance from others. - **Narrow Scope**: Focus on prioritizing what to learn next to avoid feeling overwhelmed. - **Contributing to the Team**: Wu asserts that junior developers can contribute effectively through their unique skill sets by: - **Asking Questions**: Quality questions can uncover misunderstandings and drive clarity, benefiting the entire team. - **Providing Feedback**: Constructive feedback is essential for team improvement and communication. - **Making the Team Shine**: Demonstrating team efforts in meetings through preparation and attention to detail can enhance the team’s visibility within the organization. - **Caveats and Pitfalls**: Wu highlights the risk of undervaluation of non-technical skills and the 'Girl Scout tax,' which may lead to misconceptions about women’s contributions in tech. - **Final Thoughts**: All developers, regardless of their journey, deserve to feel confident in their abilities to learn. The aim is to utilize existing skills while fostering a positive learning environment where asking for help is encouraged. Ultimately, junior developers should focus on their learning journey and the contributions they can make as they grow into their roles. By understanding and applying these principles, junior developers can more effectively navigate their early careers and leverage their diverse backgrounds to become valuable members of their teams.
Suggest modifications
Cancel
