I'll use command lines like that when I just need to get something done (after verifying that there are no files named "foo.sym"), but to write a script that uses a hard-coded filename that could stomp on other files is pretty bad. If you have a symlink foo and a file foo.sym, you've just erased foo.sym. The script also leaves all the .sym symlinks behind; it's not clear that this is the desired behavior.

If you're going to make a site and call it bash-fu, shouldn't you make sure your bash is at least good?