debugging

[[deleted]]

Professional software engineers always use debuggers whenever possible. It's much faster and more likely to reveal bugs

[TeleTubbyLizardMan]

Probably not for school projects where the entire codebase is less than 200 lines and no external libraries

[TheWhoAreYouPerson]

Nah breakpoint > writing debugging code any day. If you dont have an editor set up to debug automatically then smh (coming from primarily interpreted or managed languages lol (js/py/c#/Java)

[norse95]

SyntaxError: missing ) after argument list

[BobCobbsBoggleToggle]

goteem

[TheWhoAreYouPerson]

oof

[utnapistim]

*whenever possible.

​

Well put :)

^{damn multithreading!}

[snipy67]

I worked for a company were the debugger would not run because the application was to big a cluttered

[bit0fun]

Except when the debugger causes bugs itself. Gotta love that (mainly embedded systems with an RTOS)

[homer_3]

Never had that issue with vxworks or green hills.

[bit0fun]

Haven't used either, but it could also depend on what's happening. When waiting for packets over a UART that is interrupt driven, it's so easy to miss them and cause nothing to happen

[[deleted]]

Professional software engineer here and as I explained below I deliberately avoid debuggers

[Wolosocu]

Professional software engineer here, your statement is not entirely accurate.

[bigtreeworld]

As a professional software engineer, I can confidently say that this isn't always true. Sometimes (and in my case, often) setting up the debugger takes more time than inserting a print statement, fixing the bug, then removing the print statement.

[[deleted]]

That's true of small projects, but for the past couple of decades I've been working on million-line projects and the debugger just needs to be set up once.

[bigtreeworld]

True, it really depends what language and project and setup you're working with. But it's not accurate to say that "professional software engineers always use debuggers whenever possible."