You can assume that these file / folder names do not work on developers at the development stage, but rather an artifact of the file assembly process . JavaScript and CSS are often embedded in a single file from several source files, which includes more or less compilation / transpilation and linking steps.
The reason you want the file name to / include the hash of the file is because this causes the cache to be invalidated whenever the file changes . Static files can be cached by the browser, server, and a number of other agents between them. This is normal if the file does not change. However, when a new release is published, the user must be provided with this new version. If the resource file name changes, the browser will always request a new version of the file from the server, and not use the cached version.
You should not rely on complex file names such as this as a security / authorization function . File names are specified in the application index file and are thus known to the end user. In addition, obscurity is generally a bad idea.