Loading…
3
I finally found my missing semicolon after 3 days, it was right where I left it
Been doing basic Python tutorials for about 2 months now. Spent 3 entire evenings tracking down an error that kept saying 'invalid syntax' on line 42. Turned out I had a semicolon sitting at the end of a print statement from an old JavaScript habit. Took me forever because I kept staring at the code, not the end of the line. My buddy who codes for a living laughed and said 'we all do that once'. Has anyone else wasted way too long on something this dumb? What was your dumbest debugging moment?
1 comments
Log in to join the discussion
Log In1 Comment
nathan1008d ago
...and honestly I'm not sure three evenings is tracking it down so much as it is refusing to look at the obvious places first. The semicolon thing is a rite of passage, sure, but you could have saved yourself a lot of time by just reading the error message and checking the line end instead of staring at the whole thing like it was a puzzle. I once spent two hours fixing a CSS issue only to find out I'd typed "colour" instead of "color" and the browser just quietly ignored it. The dumb stuff is always the stuff you don't check because you assume you're too smart to mess it up that badly. I'd say welcome to the club, but you're probably going to do this again in six months with something even simpler.
3