Call me 'unprofessional' but there is a place for short and to the point beeps. Here are my two commonly programmed examples.
1. As a LOG-IN sequence for a repeated system where users have the habit of talking before the system is repeating. They 'have' to wait for the '&$%$#^%' beep before they can talk, or are reminded that they should of.
Users still gripe and moan because they can't be bothered to wait 0.185 seconds, preferring to repeat their message threeorfourtimesrealfast instead of saying it one time clearly. Example: one particular user often calls 'Evan-Oh', or at least that's what we all hear. In reality he is saying 'Eight-Seven-Two from Eight-Seven-Oh', but the first part never goes out.
2. Butt dialing. Having that irritating beep as a LOG-OUT also tells you that you just keyed up. Useful for realizing that you really didn't mean to. Or that your fire-glove-encased finger just slipped off the PTT button.
In both instances, the blips identify the radio (ANI), so we can figure out who the offender is.
And why is this considered a bad practice on stupid old analog, but the norm for 'Cutting Edge Advanced' trunking systems where you must hear a 'Happy-Chirp' before you can talk? Same concept for the guy at the wet end of the hose, isn't it?