Notice added Insufficient explanation by ChrisF
    Post Made Community Wiki by bchetty
5 Rewrite question to attempt to save it from the depths of unconstructivity
source | link

Is "Psychic Debbuging" a sign What's the benefit of good or bad developersavoiding the use of a debugger?

I'm at a "philosophical" crossroads. RecentlyOver the course of my career, I changed jobs andI've noticed once again howthat some developers do what I call "Guess Oriented Development" where most of the time the person doesn'tdon't use any debbugingdebugging tools, but instead tries hard todo spot the error from the code/db. I've come across people who were highly regarded inside the company but didn't know how to use a debugger! I noticed this with several different frameworks and in different companies.

Right now I work with a couple of guys who are not bad programmers, as far as I can tell from theirchecking on erroneous code, but they asked me why I needed to see the error that the try...catch was throwing, like I was an alien from Jupiter. And when I asked how they would debug it, they said they recheckedfigure out what the codeproblem is. 

Sure I can do that, andWhile many times thisbeing able to quickly find errors in code without a debugger is a good skill for finding more obscure problems, and as you get to know the applications better you will begin to guess the problemshave, but why would I struggle with something as simple asit seems it's less productive to spend a SQL typo?lot of time looking for issues when a debugger would easily find little mistakes like typos.

Am I beingIs it possible to manage a "debbuger minion" orcomplex without a debugger? Is it advisable? What benefits are these guys being "too hardcore"there to be had by using "psychic debugging?"

Is "Psychic Debbuging" a sign of good or bad developers?

I'm at a "philosophical" crossroads. Recently, I changed jobs and noticed once again how some developers do what I call "Guess Oriented Development" where most of the time the person doesn't use any debbuging tools, but instead tries hard to spot the error from the code/db. I've come across people who were highly regarded inside the company but didn't know how to use a debugger! I noticed this with several different frameworks and in different companies.

Right now I work with a couple of guys who are not bad programmers, as far as I can tell from their code, but they asked me why I needed to see the error that the try...catch was throwing, like I was an alien from Jupiter. And when I asked how they would debug it, they said they rechecked the code.

Sure I can do that, and many times this is a good skill for finding more obscure problems, and as you get to know the applications better you will begin to guess the problems, but why would I struggle with something as simple as a SQL typo?

Am I being a "debbuger minion" or are these guys being "too hardcore"?

What's the benefit of avoiding the use of a debugger?

Over the course of my career, I've noticed that some developers don't use debugging tools, but do spot checking on erroneous code to figure out what the problem is. 

While many times being able to quickly find errors in code without a debugger is a good skill to have, it seems it's less productive to spend a lot of time looking for issues when a debugger would easily find little mistakes like typos.

Is it possible to manage a complex without a debugger? Is it advisable? What benefits are there to be had by using "psychic debugging?"

    Tweeted twitter.com/#!/StackProgrammer/status/161546083699392512
4 Changed the title to psychic debbuging, I was not aware of the term, and it's causing quite a fus
| link

Is "Programming by Guessing""Psychic Debbuging" a sign of good or bad developers?

3 fixed spelling, otherwise improved
source | link

I'm at a "philosophical" crossroads. Recently, I changed jobs and I noticed once again how some developers, do what I call "Guess Oriented Development" where most of the time the person doesn't use any debbuging tools, but instead tries hard to spot the error from the code/db. I've come across people who were highly regarded inside the company, but didn't know how to use a debbugerdebugger! I noticed this with several different frameworks and in different companies.

Right now I work with a couple of guys who are not bad programmers, as far as I can tell from their code, but they asked me why I needed to see the error that the try...catch was throwing, like I was an alien from Jupiter. And when I asked "how do youhow they would debug this"it, they said they rechecked the code.

Sure I can do that, and many times this is a good skill for finding more obscure problems, and as you get to know the applications better you will begin to "Guess"guess the problems, but why would I struggle a with something as simple as a SQL typo?

Am I being a "debbuger minion" or are these guys being "too hardcore"?

I'm at a "philosophical" crossroads. Recently, I changed jobs and I noticed once again how some developers, do what I call "Guess Oriented Development" where most of the time the person doesn't use any debbuging tools, but instead tries hard to spot the error from the code/db. I've come across people who were highly regarded inside the company, but didn't know how to use a debbuger! I noticed this with several different frameworks and in different companies.

Right now I work with a couple of guys who are not bad programmers, as far as I can tell from their code, but they asked me why I needed to see the error that the try...catch was throwing, like I was an alien from Jupiter. And when I asked "how do you debug this", they said they rechecked the code.

Sure I can do that, and many times this is a good skill for finding more obscure problems, and as you get to know the applications better you will begin to "Guess" the problems, but why would I struggle a with something as simple as a SQL typo?

Am I being a "debbuger minion" or are these guys being "too hardcore"?

I'm at a "philosophical" crossroads. Recently, I changed jobs and noticed once again how some developers do what I call "Guess Oriented Development" where most of the time the person doesn't use any debbuging tools, but instead tries hard to spot the error from the code/db. I've come across people who were highly regarded inside the company but didn't know how to use a debugger! I noticed this with several different frameworks and in different companies.

Right now I work with a couple of guys who are not bad programmers, as far as I can tell from their code, but they asked me why I needed to see the error that the try...catch was throwing, like I was an alien from Jupiter. And when I asked how they would debug it, they said they rechecked the code.

Sure I can do that, and many times this is a good skill for finding more obscure problems, and as you get to know the applications better you will begin to guess the problems, but why would I struggle with something as simple as a SQL typo?

Am I being a "debbuger minion" or are these guys being "too hardcore"?

2 grammar and capitalization fixed, remvoed some unnecessary backstory
source | link
1
source | link