On my local server, I create aliases like these to speed up my work:
alias bashrc='vi ~/.bashrc;source ~/.bashrc;echo bashrc has been sourced' alias bashprofile='vi ~/.bash_profile;source ~/.bash_profile;echo bash profile has been sourced' alias aliases="clear;cat ~/.bash_profile|grep --color \"alias\"" alias home='cd;ls;pwd' alias root='cd /;ls;pwd' alias desktop='cd ~/Desktop;ls;pwd' alias f='cd ..;ls;pwd' alias ff='cd ../..;ls;pwd' alias fff='cd ../../..;ls;pwd' alias ffff='cd ../../../..;ls;pwd' alias pa='vim /Users/nav/workspace/someproject/src/main/resources/application.properties' alias sql="mysql -uSomeDB -p" alias updatedb='sudo /usr/libexec/locate.updatedb' alias node1='ssh -i ~/.ssh/somepem.pem firstname.lastname@example.org' alias datanode='ssh email@example.com' alias zoostart='/Users/nav/prog/zookeeper-3.4.8/bin/./zkServer.sh start' alias zoostop='/Users/nav/prog/zookeeper-3.4.8/bin/./zkServer.sh stop' alias zoocli='/Users/nav/prog/zookeeper-3.4.8/bin/./zkCli.sh'
These shortcuts allow me to work faster, as I don't have to remember long lines and some of these aliases are just one or two characters long, so I don't have to type something long either, so I used some of them on the production server too, and that's a server the other developers use too. These shortcuts can be used by them too, as they do pretty much the same work.
My supervisor differs, and says that one should never have user defined aliases on a production server. He says it's wrong of me to "use the server as your plaything".
There was one instance I remember (in a previous company where nobody had any issues using aliases) when I created aliases on bashrc and we weren't able to log on to a server via ssh, but the solution to that was to keep aliases in bash_profile instead of bashrc. Apart from that, I don't see why one shouldn't use aliases on a production server as long as the other developers are informed of the aliases. What does the community feel about this?