To keep it short, you can write your so called "elegant" coffeescript, but when it comes down to debugging the output it's going to be JS. JS _you_ didn't write.
So yeah, it's a sophomoric exercise that only adds complexity to building software. Obviously this is the #1 thing that should be avoided (unnecessary complexity) in all software. Adding more complexity is why developers _should_ get fired.
edit: Suggestions adding extra complexity to the development lifecycle do not make a case for coffeescript. They only make a case against it. That includes having to learn a useless language.
2. the generated js isn't that complex and you can easily map it in your head- it's not like trying to "debug" asm generated from C.
3. you'll get debugging soon (as wmf said, source maps- now waiting for cs guys to support in chrome, Rubymine IDE supports in D1 2013)
4. productivity is important.