Creating aliases (in your .bash_rc or .bash_aliases) can make ROS and Linux much quicker and simpler to type.
Getting to and sourcing your ROS workspace: alias setupros='cd ~/catkin_ws;source devel/setup.bash'
Consider creating aliases for commonly-used launch files (ie. alias startcf='roslaunch crazyflie_teleop start_teleop.launch'). Don't forget to add your parameters after typing your alias (ie. startcf name:=fly)
Use them; they're useful. roscd [package name] takes you to the package directory. rostopic list gives you currently advertised/published topics and rosnode list and rosparam list gives nodes and parameters, respectively. If your code/crazyflie isn't doing what you expect, check the topics or nodes; maybe you'll see the problem (wrong namespace, crashed node, etc.).