London| 26 March SDC | Jamal Laqdiem| Sprint 1 | Purple Forest/bug report/Hashtag slowing down my browser/long_bloom#221
Open
jamallaqdiem wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Self checklist
Changelist
Fixed the Hashtag Click & Routing Loop
Added JSON Body & Type Safety Guards
Questions
Reflections on working with Legacy Code:
As this was my first time dealing with a codebase I didn’t write from scratch, I found the initial phase quite overwhelming. I had to spend a lot of time mapping out the script hierarchy, understanding how the front-end routing interacted with the backend endpoints, and grasping what the application was trying to do.
My Question: In a real-world commercial environment, is this typical of a developer's day-to-day experience?
What strategies do senior developers use to quickly map out, break down, and understand an unfamiliar, large legacy codebase without feeling overwhelmed ?