A few ‘IT’ tips<\/p>\n
1. When you are looking into a problem – always check the obvious things first<\/p>\n
2. If you cannot solve a problem yourself – read the manual<\/p>\n
3. Don’t trust users to explain ‘what’ the problem is. Those are just symptoms<\/p>\n
4. Remember, computers ‘can’ make mistakes – very fast ones these days!<\/p>\n
5. Out of memory errors usually are not because of memory problems…<\/p>\n
6. Never give users more functionality than they need – otherwise you have to maintain that too!<\/p>\n
7.\u00a0 The best debugging tool is a message box (alert in js) – just don’t forget to take them out again!<\/p>\n
and some general wishdom…<\/p>\n
1. Never assume things will always go well. They generally have a habit not to<\/p>\n
2. Never underestimate the power or impact of users doing stupid things<\/p>\n
3. You only get 2 kinds of hard drives… those that have failed, and those that soon will. Apparently these days this rule applies to most hardware components…<\/p>\n
4. Crysis wasn’t created in one day, but you can play through it in a day<\/p>\n","protected":false},"excerpt":{"rendered":"
A few ‘IT’ tips 1. When you are looking into a problem – always check the obvious things first 2. If you cannot solve a problem yourself – read the manual 3. Don’t trust users to explain ‘what’ the problem …<\/p>\n