# How do you use debuggers?

**URL:** https://discourse.julialang.org/t/how-do-you-use-debuggers/4580
**Category:** Community
**Created:** [July 1, 2017, 6:41am UTC](https://discourse.julialang.org/t/how-do-you-use-debuggers/4580 "2017-07-01T06:41:52Z")
**Posts on this page:** 1
**Showing post:** 23

<div class="post-metadata">

### Author: ![jtravs](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jtravs/32/2010_2.png) [@jtravs](https://discourse.julialang.org/u/jtravs)
#### Post date: [July 1, 2017, 7:34pm UTC](https://discourse.julialang.org/t/how-do-you-use-debuggers/4580/23 "2017-07-01T19:34:52Z")

</div>

> [@antoine-levitt](#):
>
> Real Programmers who can debug code by just looking at it

There is no need to get cheeky. I do genuinely use print statements. Actually, a little more refined. My C++ code is full of DEBUG level logging and assert statements that check my preconceptions. On a normal build these are completely eliminated by the compiler. If I get an unexpected error, I run a debug build which usually quickly identifies the problem. This also has the benefit of fully documenting what I expect my code to do (useful especially with C++). I actually find this process much faster than stepping through my (often long and complex) simulations in a debugger.

But this isn’t some kind of competition! We were asked for our opinions, so I gave my experience. I definitely think having a great debugger is an asset. It’s just that when reading through the lists of [https://discourse.julialang.org/t/list-of-most-desired-features-for-julia-v1-x/4481](https://discourse.julialang.org/t/list-of-most-desired-features-for-julia-v1-x/4481) I’m a bit disheartened to read so many people wanting just a debugger and static compilation. I’d be much more interested in traits and other nice _language_ features.

---

_[View the full topic](https://discourse.julialang.org/t/how-do-you-use-debuggers/4580)._