Pretty sure the user experience folk are screaming for a path to be built there but are getting ignored.

A lot of universities with large campus grounds take the approach of observing the natural foot traffic wear patterns on grassy areas, and then build walkways where the most worn down parts are.

Its... pretty obvious.

If everyone is taking an alternate, non designed path... your design sucks, modify it to facilitate what people find more effective.

Whenever that happens, the design is wrong.

Designers need to wake up and realize their job is to understand what the user wants not what they saw in a wet dream.

I, unfortunately, have to use GitHub at $DAYJOB and this is me. I navigate most of the webpage via the URL bar now.

Basically, let's say I'm working on a repo github.com/tomato/sauce/ and want to navigate to the Releases page.

Via the webpage:

1. Type github.com into the URL bar.
2. Don't find tomato/sauce/ in the list of recent repos, even though it's the only repo I work on.
3. Click on some other repo that's at least in the tomato/ org.
4. Navigate up to the tomato/ org.
5. Find the sauce/ repo in the list.
6. Traverse half the fucking screen to hit the "Releases" heading in the middle of the About-section.

Via the Firefox URL bar:

1. Type gi→t→s→r→.
2. Hit Enter.

I admit, it's hard to compete with the latter, but I wouldn't know how to navigate that way, if the former wasn't so terrible.

!desire_paths@sh.itjust.works

"What the user needed" / "What management demanded"

This is called a "desire path." https://en.m.wikipedia.org/wiki/Desire_path

What the shit happened to that tree's shadow?

That’s right, it goes in the square hole.