Team Murder No Brain No Headache.


Relax And Debug

Most of the holiday thing is finished now and we're finally at that reprieve stage where people are supposed to rest and relax a little. I think getting older and being child-free, at least momentarily, because breaks actually feel like time off instead of the binge and purge hiring and firing often associated with holidays and poorish punk rock kids looking to pocket a little change whenever possible. It's good to be idle I guess.

I've been poking at some code and trying to figure out what some of it does. Even oh-so-orderly Python becomes a little unreadable after a year or so of being deserted. Another thing that interested me was how much more quickly I could spot potential holes in my code. Obviously when you're writing functions that basically exist to allow other functions to, uh, function the security of that particular batch of code is going to be less than airtight. I spotted a whole bunch of stuff that really sucked, though, and it's both rewarding and embarrassing simultaneously. It's also pretty rewarding to be able to go back over comments that say things like: "Fix this before some 31337 bastard owns it and causes you incredible pain," and being able to fix those things without depending entirely on documentation. I'm probably introducing new problems in the process but it sure is fun.

Speaking of which, Stani's Python Editor is a fantastic editor even though I use a bare fraction of the features baked into it. Blender is a much bigger hammer than I need for any of the trivial graphic work I do (all of which is strictly two dimensional) but it's there in case you're clinically insane or really want to jack off impress the interface freaks with some Tron-esque GUI of the future that won't ever happen. Pychecker is also in there so you can learn from the mistakes of others, wonder how long you've been making those mistakes, and how many machines are eventually going to flare up like erupting volcanos in a celebratory conflagration of your sloppy coding. Importing Pychecker as a module for in-code in-fighting is also highly recommended. All bullshit aside, I really like working with SPE and it deserves congratulations if only for the non-annoying code completion rolled in. I assume it uses PyCrust but I might be wrong because it works the same way and, more importantly, doesn't infuriate me instantaneously. I have a really hard time remembering name spaces for infrequently used libraries and modules so completion really helps when it works properly. I've used other IDEs or more bulky editors in the past that tried to do code completion for me in C++ instead of Python while insisting that I use its suggestion. Having to fight with IDEs is one of the reasons that I avoid them.

Oh, and all of that stuff that you did to your XP box because your support person insisted that you do it before they wring your technophobic neck? You have to do the same on your new machines as well. If we could just reimage people it would make support work a whole lot easier. Sticking with your old machine would probably be the safer option.

Filed under: General Comments Off
Comments (1) Trackbacks (0)
  1. Thanks for your review. SPE uses its own code completion techniques, which got improved in the latest 0.7.5.c

Trackbacks are disabled.