I definitely agree! I also usually start from business context, answering a question “how is it supposed to be working?”. This way there will also be clear division between normal (expected) things and the stuff usually described as a legacy.
This is especially important if you are coming to a complex context you are not familiar with. Modeling the main system components in my head and on paper added to code digging made it much faster for me to discover what is what.
I use paper to draw flow charts ALL the time 🙈 It's funny because the majority of the time the end result isn't even organized enough to be helpful at all, but the process of drawing it helps me understand a more organized flow in my mind...if that makes any sense!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I definitely agree! I also usually start from business context, answering a question “how is it supposed to be working?”. This way there will also be clear division between normal (expected) things and the stuff usually described as a legacy.
This is especially important if you are coming to a complex context you are not familiar with. Modeling the main system components in my head and on paper added to code digging made it much faster for me to discover what is what.
I use paper to draw flow charts ALL the time 🙈 It's funny because the majority of the time the end result isn't even organized enough to be helpful at all, but the process of drawing it helps me understand a more organized flow in my mind...if that makes any sense!