<dddddd>oops, pwd is broken (inverted require) <fossy>yeah, I was having trouble testing it <OriansJ>well I guess that is a learning experience fossy <OriansJ>anything you don't know how to automatically test, you need to manually test (which requires you to make a testing log for your own releases) <OriansJ>but use this as a chance to grown and figure out other things you don't have tests for and need <OriansJ>and patches for mes-m2's and,or,case and cond behavior are up; resulting in another working Ur-scheme tests and making it to line 2011 <OriansJ>now to just figure out why it is failing <fossy>hmm. Envars are not being passed to forked programs ***ChanServ sets mode: +o rekado
<OriansJ>fossy: because you didn't sit down with a piece of paper and think about what you are programming clearly. Then think about how to create tests or a test procedure for that very thing you wanted it to do correctly. <OriansJ>The most important lesson that programming teaches you is: you will make mistakes even when you think it is impossible for you to do so. <OriansJ>Then it is the techniques that specific to you, help you reduce the number of errors you make and reduce the amount of effort required to find them. <fossy>OriansJ: one thing this whole process has especially taught me the importance of tests <fossy>the only things broken have been things not covered by tests