+ 3
Does a programmer "FEEL" the code?
Did it happen to you when you were doing a challenge , and just before you submit your answer , you "FELT" your answer was wrong and it was so. How many times you were writing a code and something told you that you were going in the wrong direction, it doesn't tell you why it is wrong , but it "FEEL" like so . Does this happen to you , how often , and do you count on it ?
6 Antworten
+ 3
@Rabee " it just doesn't work right or compiler yells at me" - I covered logic and syntax. ;)
And yes, I agree with you, intuition is useful in most aspects of life. My intuition with programming usually comes in the form of how I can just flow into my problem without having to overthink it usually. It's still good to have your structure and plan, but the blanks in between it does wonders. However, experience and simply spending endless hours debugging is what has helped me out the most with how I program. Intuition does nothing for me there. In the business world I currently exist in, intuition must include reason also.
It all has its place with how I do things, and most of the time my intuition shows up in my ideas/direction that I go with my goals. I get a feeling for what to create, and I listen to my gut on it.
+ 2
I don't get a feeling, it just doesn't work right or compiler yells at me. Then I go "hmmmmmmmmmmmm" and grind it out until it's what I want. I try to be a confident person though, so I always feel like it's going to work. :D However, that's a great reason why one should map things out prior to writing their code. Doesn't prevent bugs, but it does make it a lot easier to know what direction you're going, and the flow of your program. If you plan for it to work, then it works out better. Besides, nothing worse than getting far into something and then realize you need to do it a completely different way to get what you're wanting. :D
+ 2
and by the way , if the compiler doesn't complain , it doesn't mean the code is right,
+ 2
"blanks in between makes wonders " u hit the point exactly, thanks
+ 1
It's called doubt and it doesn't just ruin your codes but your relationships as well.
+ 1
what I meant to say is that reasoning is not the only way to solve a problem , and sometimes even the most logical issues can be solved with intuition