as usual. Write code gets borked. beat head against wall for a day or so. Ask for help. Solve it within an hour.
-
something small of course. I even asked for help from Code Project Quick Answers. I am sure they would have solved it for me. Co-worker stops over. Points at one line and says do this. Yep that works. Always the same. When you stop to ask. It solves itself. You would think after 30+ years of programming I would know this. Now to go clean it up and make it good code. Thanks all.
To err is human to really mess up you need a computer
It's a small world after all :-\
-
something small of course. I even asked for help from Code Project Quick Answers. I am sure they would have solved it for me. Co-worker stops over. Points at one line and says do this. Yep that works. Always the same. When you stop to ask. It solves itself. You would think after 30+ years of programming I would know this. Now to go clean it up and make it good code. Thanks all.
To err is human to really mess up you need a computer
-
something small of course. I even asked for help from Code Project Quick Answers. I am sure they would have solved it for me. Co-worker stops over. Points at one line and says do this. Yep that works. Always the same. When you stop to ask. It solves itself. You would think after 30+ years of programming I would know this. Now to go clean it up and make it good code. Thanks all.
To err is human to really mess up you need a computer
Time to talk to the [rubber duck](https://rubberduckdebugging.com/)? I usually find bugs when I spend the time to write up a question to satisfactorily explain it to whoever I am asking. This usually starts after several hours of banging my head against a variety of hard surfaces. 30+ years of building up 'get it done' habits are hard to overcome!
I'm pretty sure I would not like to live in a world in which I would never be offended. I am absolutely certain I don't want to live in a world in which you would never be offended. Freedom doesn't mean the absence of things you don't like. Dave
-
Time to talk to the [rubber duck](https://rubberduckdebugging.com/)? I usually find bugs when I spend the time to write up a question to satisfactorily explain it to whoever I am asking. This usually starts after several hours of banging my head against a variety of hard surfaces. 30+ years of building up 'get it done' habits are hard to overcome!
I'm pretty sure I would not like to live in a world in which I would never be offended. I am absolutely certain I don't want to live in a world in which you would never be offended. Freedom doesn't mean the absence of things you don't like. Dave
-
Well I wrote it earlier - I just didn't post it when I wrote it (this thing called work (shudder) got in the way. Now I just look like I'm repeating things. :doh: Now I just look like I'm repeating things. :doh: Now I just look like I'm repeating things. :doh:
-
Rubber Duck Debugging – Rubber Duck Debugging – Debugging software with a rubber ducky[^] :-D
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Many times I have solved my own problem by just talking about it with a co-worker. It forces a different way of thinking and the solution often just presents itself. I have stopped my explanation in mid-sentence, said "oh, that's it", end of story.
My rubber duck co worker gets really pissed with me, not explaining the entire problem really annoys him!
Never underestimate the power of human stupidity RAH
-
something small of course. I even asked for help from Code Project Quick Answers. I am sure they would have solved it for me. Co-worker stops over. Points at one line and says do this. Yep that works. Always the same. When you stop to ask. It solves itself. You would think after 30+ years of programming I would know this. Now to go clean it up and make it good code. Thanks all.
To err is human to really mess up you need a computer
My personal experience, whether you "understand" your code or not, try explaining it to someone else. If it takes more than a few paragraphs, try again. I'm a true believer that explaining your code to the "uninformed", successfully or otherwise, will enhance your own understanding of it.
-
Hey, this is 2018 : Anything that is more than 15min old does not exist anymore (apart from your embarrassing pictures from 1982 on social media).
-
Many times I have solved my own problem by just talking about it with a co-worker. It forces a different way of thinking and the solution often just presents itself. I have stopped my explanation in mid-sentence, said "oh, that's it", end of story.
Yup I hear you. I think it has to do with the fact that when you are dealing with it yourself you have too much internal tacit knowledge about your solution. Having to go back to first principals to explain it to someone else often shows you where this internal knowledge is wrong but you have moved past that part of the problem.
The only thing unpredictable about me is just how predictable I'm going to be.
-
My personal experience, whether you "understand" your code or not, try explaining it to someone else. If it takes more than a few paragraphs, try again. I'm a true believer that explaining your code to the "uninformed", successfully or otherwise, will enhance your own understanding of it.
Eric Lynch wrote:
My personal experience, whether you "understand" your code or not, try explaining it to someone else.
Do it out loud, and people will say you're crazy.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
My personal experience, whether you "understand" your code or not, try explaining it to someone else. If it takes more than a few paragraphs, try again. I'm a true believer that explaining your code to the "uninformed", successfully or otherwise, will enhance your own understanding of it.
-
*Internal batman voice intensifies* Why do you wanna debug with me?[^]
