they look at the system with fresh eyes and can spot patterns people too close to the problem have learned to ignore. I'll cover how you can do this later in the post.
When you mention "the parts of SDLC that others often overlook," how can I train myself to notice these risks earlier as an individual who just started working in the SRE space and has limited knowledge of the SDLC?
Quite simply, you'd note at your work that engineers talk about certain aspects of the software more than others. The ones that are not discussed as often aren't necessarily given the amount of attention that they should be given, and that is a good place to start.
When you mention "the parts of SDLC that others often overlook," how can I train myself to notice these risks earlier as an individual who just started working in the SRE space and has limited knowledge of the SDLC?
Quite simply, you'd note at your work that engineers talk about certain aspects of the software more than others. The ones that are not discussed as often aren't necessarily given the amount of attention that they should be given, and that is a good place to start.