We use DevPartner which seems to work pretty well for me. It's fairly neat the way it works. Although it does seem to identify some things as memory leaks that probably aren't actually leaks (ResultSets, IBM MQ Series objects, etc), if you limit the check to your own packages, a lot of your in-house errors will stand out right way and it will ignore the (assumed) false spots. Give it a try.
You seem to be a popular and well-liked employee, is there any chance of getting a transfer to a position inside your company that you might enjoy more? I'm sure they'd hate to lose you.
One thing to keep in mind with List.size(), that method is not limited to Lists (something similar to arrays), but rather any type of Collection. The 'length' of a Set doesn't make much sense, but size tends to.
It is a little odd at first, but mathematically and logically, I find it appealing: length of a vector and the size of some generic collection.
Evil? Come on now, when it really comes down to it, he's trying to save a few lives; that's a lot more important than being a jerk in the business world. He was mean, got away with it and made some money, at least he's trying to do some good with what he's got and that's a lot more than most people, rich or not can say.
I try this, but you know what annoys me? When I put very complete and explanatory comments in code, then sit down with someone to review the code and the first thing they do is skip past the comments, look at some assignment and ask me why I'm doing it. I mentally sigh and point to the comments. I put those comments there for a reason, read them! If you're still confused, I clearly need to add more, but at least give them the benefit of the doubt. There are so many lazy programmers on both side on the comments.
Makes me wonder if a good lawyer wouldn't fill a QA/testing type of role with high capabilities. We could use more people with an eye for loopholes and supposedly impossible cases.
Slashdot Mirror
We use DevPartner which seems to work pretty well for me. It's fairly neat the way it works. Although it does seem to identify some things as memory leaks that probably aren't actually leaks (ResultSets, IBM MQ Series objects, etc), if you limit the check to your own packages, a lot of your in-house errors will stand out right way and it will ignore the (assumed) false spots. Give it a try.
You seem to be a popular and well-liked employee, is there any chance of getting a transfer to a position inside your company that you might enjoy more? I'm sure they'd hate to lose you.
One thing to keep in mind with List.size(), that method is not limited to Lists (something similar to arrays), but rather any type of Collection. The 'length' of a Set doesn't make much sense, but size tends to.
It is a little odd at first, but mathematically and logically, I find it appealing: length of a vector and the size of some generic collection.
Evil? Come on now, when it really comes down to it, he's trying to save a few lives; that's a lot more important than being a jerk in the business world. He was mean, got away with it and made some money, at least he's trying to do some good with what he's got and that's a lot more than most people, rich or not can say.
I try this, but you know what annoys me? When I put very complete and explanatory comments in code, then sit down with someone to review the code and the first thing they do is skip past the comments, look at some assignment and ask me why I'm doing it. I mentally sigh and point to the comments. I put those comments there for a reason, read them! If you're still confused, I clearly need to add more, but at least give them the benefit of the doubt. There are so many lazy programmers on both side on the comments.
I go by these two sites every day or so to see if anything catches my eye, good deals, usually.
Passwird.com
Spoofee
Makes me wonder if a good lawyer wouldn't fill a QA/testing type of role with high capabilities. We could use more people with an eye for loopholes and supposedly impossible cases.