From 0032d0a4e1bb0c1ed0c9aa6ad44d23f2f4aded6e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=2E=C3=87a=C4=9Flar=20Onur?= Date: Wed, 26 Oct 2005 20:52:31 +0000 Subject: [PATCH] CODING continues... --- CODING | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CODING b/CODING index 653e5b21..5e4800b0 100644 --- a/CODING +++ b/CODING @@ -15,6 +15,17 @@ Guidelines 6. If you are changing something, check if that change breaks anything and fix breakage. For instance a name. Running the tests is not always enough! +7. We all know, you're using LISP but didn't want to tell + us. Don't scare, as a success story and for your encouregment + there are tens of people on somewhere with LISP releated jobs. +8. If you are studying Data structures and Algorithms, and if + your first assignment is implementing a basic stack for + presedence, don't implement it. Just show your teacher the + syntax of LISP, tell him how beatifull it is, and show how can + otistic person can count lots of paranthesis with "one second" look, + probably you'll get A+. +9. If you are interesting with "Playstation 2 Linux Games Programming" + or "How to extend C programs with Guile", please don't. Unit testing ------------