When I first downloaded FF5, none of my favourite add-ons worked. Things are rapidly getting better, but I still miss my Delicious bookmarks button.

KramII

I organise my code in the One True Way - the way everyone should. 1. One file = one class, period. 2. Using statements at the top of the file, before anything else (except header comments). 3. Backwards: Private methods first, then public methods, then public properties, then constructor, then static methods. The idea is that readers get to know what each method property does, working from the inside out. When you get to the constructor and it calls a method called "PerformQuirkafleeg", you already know what a Quirkafleeg is and what happens when you perform one. 4. I think about code organisation all the time. Unfortunately, this means I change my mind quite often... but whatever I think at any given moment is "The One True Way", and should be followed by everyone.

KramII

You've obviously got two smart devs working for you!

KramII

You should probably stop paying the person who is leaving.

KramII

Both, actually... but a point well made nonetheless.

KramII

Since the demise of the Pink Elephant, Fawcett road just isn't the same. :((

KramII

I feel your pain. As a programmer, however, I can't answer your question. Instead, I am obliged to point out that you're trying to solve the wrong problem. Suggestions: 1) Buy lots of pairs of generic black socks that will suit everyone. 2) Buy yourself distinctive socks, and let everyone else fight it out between themselves. 3) Get everyone to stop wearing socks. Bin all existing socks. 4) Clip socks together when you take them off, and leave them clipped in the wash. That's how many blind sock-sorters achieve good results. 5) Buy everyone distinctive socks. Eg. you = purple, younger son = pink etc. 6) Ask wife to demonstrate how to sort socks - either learn from her, or (better still) keep asking for repeat demos. 7) Do each person's laundary separately. 8) Learn to make pie - sounds like much less difficult. 9) Send me pie. It won't solve the sock problem, but I do like cherry pie. Mmm... pie.

KramII

I won't even say if I *have* any security. Nor anything to secure. Nor who, in fact, I really am. If anybody... :-D Anyway, back to (what passed for) reality. eWallet 7.0 from Illium software might be worth a look. I must admit, however, that I have yet to try it, but I have been using an earlier version (without browser integration) for years, and have found a great little wallet app for storing passwords and all sorts of other info. But shh... don't tell.

KramII

No, no, no! British: It's a tin.

KramII

Doh!

KramII

In that case, it sounds fun. All the best with the project.

KramII

The project sounds interesting, but... Considering the man-hour cost of writing your software, I honestly wonder if you wouldn't be better off putting your money into better (faster) hardware?

KramII

... vote this down for me, You're a troll and there is no place immune to you. Hey! Mr. down-voter, vote this down for me, In the jingle-jangle morning I'll be down-voting you

KramII

For larger files, I suggest carrier ostritch.

KramII

The people who make that thing - they're just taking the p***.

KramII

This is pure anti-varist propaganda. If there is an enemy in the camp, it is not var. The much-maligned VB party strives not for anarchy, but for freedom with responsibility. The VB party does not condone any acts of violence perpetrated with var or any other tool at our disposal. We do seek to free, but we also strive to educate. Now, we do openly acknowledge that there are those within out ranks who misappropriate the libertarian message of var, who misuse its expressiveness to undermine productivity and pollute the code-base. However, var is not the cause of poor practice, but merely a tool of convenience for the unlearned hack. Take away var and these uneducated code-manglers will find a myriad other techniques to defile your code. They will tangle your classes, force your file handles permanently open, race your threads until they lock, or leach your resources with their crude algorithms and ugle data structures. So, we recognise that there are those who misuse the tools we provide, but argue that this is true of every party, regardless of colour and flag. And may I say this to those who besmirch the good name of the VB party: you speak of the impurity promoted by var, but ignore a greater danger: providing unregulated access to the world of unmanaged code, a realm where the uninitiated are free to dangle their pointers without reprise nor censure! He who is without sin, my friends, he who is without sin.

KramII

jschell wrote:

Avoiding deep-nesting is a negative assertion. By not doing something there is a positive benefit.

Oh, I see what you're getting at. In that case: Use shallow nesting. Is that positive enough for you? :rolleyes:

KramII

jschell wrote:

I would like to see a positive assertion about code structures which measurably impacts code quality. That would be analogous to your assertions about patterns.

The structures that McConnell proposes to avoid deep-nesting (1) are positive (2) measurably impact code quality. He provides *hundreds* similar examples. I agree with your comment about the benefits of code reviews - these can be very useful for improving code.

KramII

I am not aware of McConnell placing a monetary value on his arguments. However, he does make a strong case for many code construction practices. For example, McConnell (pg. 445, CC2) references a number of studies that imply that nesting if statements more than 3 or 4 layers deep makes them difficult to understand for most programmers. He then goes on to describe methods to avoid deep nesting in actual code construction.

KramII

You mean you're not all my best friends? You wouldn't just drop everything and come visit me in my hour of need? And I thought you *all* wanted my babies! :^) I need a hug! :-D

KramII