Back when I was doing C# development I would use the Visual Studio debugger all the time and was pretty happy with it. When I moved to doing Clojure and Clojure

Back when I was doing C# development I would use the Visual Studio debugger all the time and was pretty happy with it. When I moved to doing Clojure and ClojureScript I decided to learn emacs and stopped using a debugger until I learned about the debugger in Chrome when using clojurescript dev tools (it will allow you to set breakpoints in your ClojureScript source in the Chrome Developer Tools console). My technique for debugging with Clojure + emacs was to use a bunch of print statements and then also using a repl to try and duplicate the issues or at least see what was going on. Less than a month ago I started using the CIDER debugger inside emacs and have been happy with it overall. There are some issues I have had, namely that you can't set breakpoints in macros which is understandable. I have gotten around that by creating a temporary function and move all the code into that function. The main use case I have for doing that is when trying to debug Compojure routes, which are defined in macros.