What is the best approach to solve a bug or implement features that involve external codebases?
Mid-Level Software Engineer at Intuit6 months ago
As part of my story or task, often times I have to understand and contribute to other codebases or solve bugs that involve understanding flow of other codebases. What is the best way to navigate this when you are suppose to solve an issue where you have to understand an external codebase in order to contribute or fix an issue?
0 Likes
77 Views
2 Comments
👑
![Mid-Level Software Engineer [E4] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta.jpeg%3Falt%3Dmedia%26token%3Da7a5bcc0-e178-4b5b-b71e-09bf6c6aefae&w=48&q=75){kind=small}
Discussion
(2 comments)
6 months agoMid-Level Software Engineer [OP]IntuitAlready found what I was looking for. Thanks so much for creating this community: https://www.jointaro.com/question/ZRneLgwmrM2JLCrGn5Rz/im-trying-to-fix-a-p1-bug-but-some-relevant-code-is-owned-by-another-team-unsure-about-ownership-and-how-to-proceed/
1 Like- 6 months agoTech Lead @ Robinhood, Meta, Course Hero
I hope these other resources are helpful as well!
- "How can I root cause bugs faster?"
- "How can I become more independent and better at unblocking myself with tricky technical issues?"
- "What is the effective way to understand new repository in order to make the required changes in that repo?"
Summarizing all the wisdom from these threads:
- Be excited about these opportunities and treat them as an opportunity to collaborate with others and expand your learning.
- Bias towards action. Try changing the code and seeing what happens. Add all the log statements ever and see what surfaces. Don't get stuck reading.
- Understand the overall flow end to end. Everything in tech is a series of steps.
0 Likes
