Yesterday I learned that it is NOT a good idea to run a command that you are pretty sure is wrong. Yeah, I know. Seems obvious now. But I was getting tired of being all paranoid and obsessive-compulsive with everything, all the time. I'm always pouring over every little detail, checking things like three times before I do anything risky. Yesterday I thought I'd be a little more aggressive. I mean, how would Wolverine program? He wouldn't examine every detail, fretting about what could go wrong. He'd just be like "lets see what happens."
Which is exactly what I said, out loud, when I entered something on the command line that my office-mate insisted would work. I had asked him how to do something, and he showed me a command that looked wrong. I just kind of went with it, wondering what could possibly happen. The answer to that question, my friend, is that I completely screwed up my toolchain. I barely know how to use this stuff, let alone fix it. I was quite the unhappy camper. I finally fixed it today, after hours of pouring over troubleshooting documentation, deleting random things, and re...something a lot of things. I still don't know what went wrong, or how I fixed it. What's important is this stupid system is working again. For now. Also I'm not going to be entering any more random commands without thinking first. Also, I learned that having a confident, "whatever happens, happens" attitude towards programming basically invites disaster.
Speaking of disaster, code that I wrote is off, squirreling its way through a testing/qa process that will eventually land it in production. I tested it myself (as best it could) but I'm not entirely sure it will work right. I've been joking with everyone saying stuff like "yeah, so if your order doesn't go through its my fault," but I just realized that could actually happen.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment