Bits of Wisdom

You know when your program is useful when you spend more time using it then developing it.

Stressing over having a correct object oriented design is Just Another Form of Premature Optimization.

Make it work.  Then optimize.  Never the other way around.

Always use linked lists for everything.

C++ is superior to all variants of LISP.

Don't be a "fan" of one specific language/paradigm. Try to learn as much as you can about all languages.

>>5
It's a matter of preference.

>>6
I'm just going to take a moment to stop trolling and say that you aren't a true software developer / computer scientist without a love for learning new frameworks/languages.  Every new tool you collect makes you more efficient and knowledgeable.  Even PHP (it teaches you how to not design a scripting language littered with C bindings).

Don't trust books that speak to you like a seven-year old.

>>9
You're referring of course, to Structure and Interpretation of CP?

>>10
Structure and Interpretation of Child Porn, yes.

>>4
finger tree was here, linked list is a faggot

The most important thing you'll ever read is SIWJ (Structure and Interpretation of Wooden Joints). If you can't find a copy of this book, K&R have created a fine book called 'The Joint Carpentry Language' which talks in depth about the art of mortise and tenon joints (something which SIWJ sorely lacks).

Don't free all your malloc's.  Free is a very expensive code no matter how you measure it, and the OS will take care of it when your program exits.  If you aren't coming close to running out of memory, let it leak 'till the program exits and let the OS do the work.  It will make your program run up to ^x16 times as fast.

>>14
What? You are kidding right? To the readers at home, I would not recommend intentionally leaking memory in this manner.

>>14
I do that, no worries.

>>15
Are you new to programming?  That's one of the oldest tricks to make your programs more efficient.  It's not for novices, though.

Ensure that all of your local variables are set to null or 0 at the end of their scope, so the computer knows they're finished being used, like so:

int Add(int valueToBeAddedToBySecondArgument, int valueBeingAddedToFirstArgument)
{
    int temporaryValueOfTheFirstAndSecondArguments;
   
    if(valueToBeAddedToBySecondArgument == 0)
    {
        temporaryValueOfTheFirstAndSecondArguments = valueBeingAddedToFirstArgument;
    }
    else if(valueBeingAddedToFirstArgument == 0)
    {       
        temporaryValueOfTheFirstAndSecondArguments = valueToBeAddedToBySecondArgument;
    }
    else
    {
        temporaryValueOfTheFirstAndSecondArguments = valueToBeAddedToBySecondArgument;
        temporaryValueOfTheFirstAndSecondArguments = temporaryValueOfTheFirstAndSecondArguments + valueBeingAddedToFirstArgument;
    }

    valueToBeAddedToBySecondArgument = 0;
    valueBeingAddedToFirstArgument = 0;

    return temporaryValueOfTheFirstAndSecondArguments;

    temporaryValueOfTheFirstAndSecondArguments = 0;
}

If you do not do this your computer will run out of memory very, very fast and can cause a virus to infect your motherboard!

when photographing windmills, always attach a handkerchief to one of the sails. This will provide invaluable information on wind direction and sail rotation when the picture is developed

>>18
That actually helps optimize the code for the assembler.

>>14
Even better - write your own memory allocator!

<-- check em dubz

24 Name: tray 2012-03-14 16:17

you better be