I believe it depends on the latitude, since away from the equator the Sun rises at an angle and not straight up. It can be low enough to still be below the visor, but risen enough to have moved far enough south (if in the northern hemisphere) to be problematic when driving southeast in the morning or southwest in the evening.

I found this image on Google search that I think illustrates the phenomenon: https://share.google/okYRf16lB1vegnVax

http://stevekluge.com/astronomy/riseazimuth.html

At the Equator, where the Sun rises and sets perpendicular to the horizon, the Summer Solstice Sun rises 23.5° north of due East, and sets 23.5° north of due West.

The Sun moves around a lot over a year. I don’t think it’s practical to try to plan a grid around it.

I get the “notified teams, they did nothing” frustration, but I have seen how it can happen with low-maintenance features in departments with turnover. Team has one tech-minded person who sets up $feature, it fills a team need and gets embedded in business routines and just works, no one has any idea where it came from other than, for a while, $techieTeamMember had something to do with it. Techie person moves on in their career, other team has turnover and as a result team completely loses even vague tribal knowledge of where $feature comes from, or especially if it is embedded inside another user interface, what it is called. Now notifications of $feature breaking are completely meaningless to the team - they don’t associate any words in the email with the thing they use.

It decreases the need for accuracy when used with shot. In a longer barrel, the shot will expand in a relatively small cone. Coming out of a short barrel, everything in the general vicinity in front of you will get little damaging pieces embedded all over their body.