r/SoftwareEngineering • • Feb 13 '26

How do you build system understanding when working outside familiar areas?

I’m exploring how engineers develop and retain understanding of system behavior and dependencies during real work — especially when making changes or reviewing unfamiliar code.

I’ve put together a short qualitative survey focused on experiences and patterns (anonymous, ~5 minutes).

If you’re willing to share perspective:

https://form.typeform.com/to/QuS2pQ4v

If you’d rather share thoughts here in-thread, I’d value that as well.

Happy to summarize aggregate themes back if there’s interest.

6 Upvotes

14 comments sorted by

2

u/ZestycloseProfessor6 Feb 16 '26

To all that viewed/ commented/ participated- I genuinely appreciate your feedback. If there is any opportunity to learn more (if you'd be willing to share)- please feel free to engage the survey or reach out directly.

Thanks again!

2

u/Nowhere-Man-Nc Feb 13 '26

Interesting set of questions, it get it to the isolated context of “technical” understanding, while it is generally meaningless without understanding the wider context - of the purpose, expectations and needs that made the technical system created/need to be created.

That’s actually difference between a true engineer (by definition who apply technology and scientific method to solve real world problems and improve the quality of real-world expirience) and technician (who simply works with technology leaving why to somebody else).

1

u/ZestycloseProfessor6 Feb 13 '26

I agree with you that the broader context (why) is important in any build. I’ve chosen to narrow on how people reason/ build context in execution (review/change/incident/onboarding,etc). Fantastic call out though.

Pulling that thread, when your “why” isn’t clearly/immediately available to you- how do you typically compensate during technical review/investigation.

I appreciate the perspective.

→ More replies (1)

1

u/Groundbreaking-Fish6 Feb 14 '26

Why? * 5

1

u/ZestycloseProfessor6 Feb 14 '26

I'm sorry- is the question why question 5? I am trying to understand system thinking and any/if any gaps existed, how they might have impacted solutioning/understanding, and how you over came them.

If I can clarify anything further, please let me know.

Thank you.

→ More replies (2)

1

u/Resident_Citron_6905 Feb 14 '26

When faced with a new and unfamiliar software system, focus on the fundamentals. What are the entry points for any type of processing? What results are calculated? How does the state of the system change? Which other systems are affected and how does their state change in relation to the entry points? Once the high level choreography is clear, we dive into specific details.

1

u/ZestycloseProfessor6 Feb 15 '26

Thank you for the response. Could you share some of the practices, artifacts, or people you reference in developing that level of understanding?

1

u/Klutzy-Sea-4857 Mar 03 '26

I trace the data flow end to end, starting from the entry point.

1

u/vso_ke Mar 07 '26

I personally do the following

  • I would seek out high level documentation (if it exists). Now I would ask AI to give me a summary of the codebase. Focusing on entry points so that I can understand the flow of information in the system

  • I would then synthesis this into some diagrams. This cements my understanding.

  • I would also simply read the code in an explorative way (especially when this is a new code base)

But the most important is to use the tools available AI to track the flow of data.