• 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle




  • Personally, I would say to pick a specific implementation instance and debug it.

    Let me use a button as an example.

    If you have a button, say, Subscribe, attach your debugger where execution will go immediately upon click. Follow the path by stepping into (not over) the base implementation(s). Stop along the way if there are any calls that you do not understand what it is doing or why.

    I most scenarios, there is common functionality that all objects would need. All buttons need to do x, y, z. All forms need to validate a, b, c, and forms of this specific type also need to validate d.

    Usually the tradeoff in complexity upon first learning the code base is offset by the ease of extensibility once you are familiar with it.