• meteorswarm@beehaw.org
    link
    fedilink
    arrow-up
    7
    ·
    1 year ago

    Ironically, as I’ve become more senior (11+ years at a faang company) I’ve had to do less and less of that “look around and understand everything” work because of time pressure. But I rely on my experience to be more confident that I can ignore the details and focus on the reason I’m in this file.

    Well, that, and if it gets too messy I give up and call in a junior engineer…

    • pixelscript@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Yeah, how much time you get to dwell on it will depend on lots of factors and the needs of your client/employer.

      I happen to work at a place where timeframes for fixes are quite lax, and the codebase I’m working with is slowly being recussitated from a decade of bad decisions from a D-tier web developer. (Dreamweaver was involved… let’s leave it at that.) I can imagine if you have a codebase that was somewhat competently designed from the start and/or your client/employer has a “I need this fixed yesterday or else your ass is FIRED” urgency, you don’t have time to dwell on such things. But it helps to have the experience that at least lets you do it a little bit rather than not at all.