Out come the "this is dumb because .." messages in the redit responses.
I have experiences dozens of projects where the developer had the wrong view of the end use needs for a myriad of reasons (everything after the because). It doesn't matter why in this case just that they found their solution.
The TL;DR message should be make sure the real needs get serviced.
In the days when perl was the language of choice for the web I got a 97% reduction in code size. I was asked to join a late project to speed it up. (Yes I know that has low success rate).
The lead dev was a hard core c programmer and had no perl experience before this job. He handed me a 200 line uncommented function that he wrote and was not working. It was a pattern matcher. I replaced it with 6 lines of commented perl with regex that was very readable (for a regex).
Since he had no idiomatic understanding of perl he did not accept it and complained to management. We had to bring in the local perl demigod to arbitrate(at 21 was half my age at the time, but smart as a whip). Ruled in my favor and the lead was pissed.
I am the MapGuy(TM). I had paper maps of every destination and triptix from AAA. I would fly with a pocket Rand McNally Road Atlas and be able to identify where we were from features on the ground. I still do it but I use a GPS. I don't trust them so I still check maps before I use a GPS in unfamiliar areas. I find badly optimized routes 5% of the time and outright mistakes 1%.
I was the one who got people unlost when they got them selves lost because they did not listen to the map geek.
I hope this gives me at least 30 more years before mental decline starts. That will get me to my late 90's.
The TL;DR message should be make sure the real needs get serviced.