Silly / Small Bugs / "Typos"

Newbie & Debugging Questions
#1

So yea. I guess this thread belongs in debugging section, because it is about debugging :smiley:

What the problem I have is that my theory and implementation is usually “near perfect” to what I want. Just now I made something and it didn’t work properly. I was looking through huge chunks of my code to find the possible error. And the error was that I made a “typo”, but with variable. Was supposed to be i / width, but I typed i / height. I knew how it was supposed to be, but I just wasn’t thinking about what I was typing at that moment. That took away 10 minutes of my precious time :frowning:

And this happens all the time for me :smiley:

Do you get these “typos” ?

#2

always…i mean never!!

#3

Who doesn’t?..

#4

Me.

#5

You have to tell me how!

#6

I luck at the keyboard.

#7

Yeah… Can’t avoid em. Part of being human and all that :stuck_out_tongue:

#8

Everyone does it.

#9

@Troubleshoots
On how many projects where you have to have tonnes of classes to make it just runnable did you work?
I cannot believe you that you manage those without making those logical mistakes at least sometimes.

#10

I’m relatively new to programming in general so the answer would be not many, however I’m currently working on two libraries where one is being designed based on the design of the other. So far (I’ve finished about 10 classes and working on 8 more at the moment) I haven’t made any logical mistakes (I’ve done some testing). My only problem is getting confused with what I’ve completed, as I have to work on multiple things at once and refactor as I go along. I guess that just comes down to poor organisation of my time.

Regarding previous projects, I’ve never made a mistake where I’ve mistyped something. The mistakes I make are usually forgetting a line, or a wrongly used operator (e.g <= instead of <).

#11

This is exactly what we were or at least I was talking about.

#12

I mostly make copy pasta errors.

  1. Write correct line for X.
  2. Copy-pasta for Y and Z.
  3. Fail to completely update the pasted lines to work correctly.
  4. ???
  5. Profit!
#13

#14

Very close to pure spam…

#15

I was just pointing out the typo in an immature way.

#16

Yep. You did^^

#17

99.5% of my bugs that require any time to track down are in code so simple I know it’s correct.

#18

I get these all the time. I wish there were Logic Debuggers that sense (through that mental conection that you have with your computer :wink: ) what you want to do and then finds any errors in it. Such a thing seems impossible but would save programmers a lot of time

#19

If we had that we wouldn’t need programming languages in the first place.

#20

touche