![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
snarp(Very little of this post will make sense to you if you have never wasted eight hours trying to induce a C-derived programming language to perform an elementary task.)
Usually when you are coding something and you can't figure out what the problem is, it is your problem; it is not the programming environment's problem, and insisting to your CS professor that it is will avail you of little. I have generally found it most productive to assume at all times that I am the one with the problem, and thus to continue banging my head against the keyboard until I figure out what it is.
Well, I've been working under that assumption for a few hours now. I went on Google just now, and darnit, Microsoft. You're gonna ruin my work ethic here. How can I force myself to keep screwing with my code if I can't be sure whether I'm the problem or not? I mean, this thing that is broken is not complicated! It's relatively simple, and it's very troubling when something simple doesn't work! I am losing my faith; it's like when there's a Long Interval in Dragonriders.
Usually when you are coding something and you can't figure out what the problem is, it is your problem; it is not the programming environment's problem, and insisting to your CS professor that it is will avail you of little. I have generally found it most productive to assume at all times that I am the one with the problem, and thus to continue banging my head against the keyboard until I figure out what it is.
Well, I've been working under that assumption for a few hours now. I went on Google just now, and darnit, Microsoft. You're gonna ruin my work ethic here. How can I force myself to keep screwing with my code if I can't be sure whether I'm the problem or not? I mean, this thing that is broken is not complicated! It's relatively simple, and it's very troubling when something simple doesn't work! I am losing my faith; it's like when there's a Long Interval in Dragonriders.
