GOOD PROGRAMMING
Download as PPTX, PDF1 like195 views
The document discusses common fears and challenges that programmers face such as self-doubt in their abilities, messy code formatting, inconsistent naming conventions, over-commenting, not fully understanding their programming language, and thinking they know everything when they are still learning. It provides tips for overcoming these issues such as taking time to plan their program logic, using a modular approach to break problems into smaller pieces, commenting code as needed, indenting code properly, and continuously learning through books, blogs, and hands-on practice.
GOOD PROGRAMMING
- 1. 1
- 2. WHAT IS PROGRAMMING ? Process of writing computer programs Creative process that instruct a computer on how to do task 2
- 3. 3
- 4. FEAR AND SELF DOUBT Think you're not good enough, not smart enough: that you have the wrong type of brain, and you'll just never get it. 4
- 5. MESSY CODE FORMATING Didn’t indent your code Inconsistent use of new lines and white space 5
- 6. Inconsistent use of upper and lower case letters Uses both cases of letters 6
- 7. Bad variable and function name Single name variables No relation between variable and its function 7
- 8. Over-commenting Commenting on every step Uses useless comments 8
- 9. Not knowing the full expressive power of your language Don’t have the knowledge of operators Confusing between syntax of two languages 9
- 10. Thinking u know it all Thinking yourself a professional Forgot that you are learning 10
- 11. 11
- 12. Patiently read the full question or listen the instructions Make a rough sketch 12
- 13. Think about the logic of program and then think about the method you are going to use 13
- 14. Take the time to write down what goals the end product needs to achieve, and who your user base will be. Clarity of thought at this stage will save a lot of time down the line. 14
- 15. Go to modular approach that is divide your task into small fragments 15
- 16. If you think that your code might need explanation, comment it. Remember to update the comments when you update your code! 16
- 17. Indent your code 17
- 18. Start by testing each module on it's own, using inputs and values that you would typically expect. Then try inputs that are possible but less common. Incorrect values. Use zero for a value that will be used in division, or a negative number when positive is expected or when a square root will be calculated. 18
- 19. Programming is not a stagnant discipline. There's always something new to learn, and - perhaps more importantly - always something old to relearn. 19
- 20. Take responsibility for your own career Q/A yourself 20
- 21. When programming something complex, it helps to get the simpler building blocks in place and working properly first. This approach naturally lends itself to modular code writing, where each component is in its own self-contained block. This is very useful for code reuse and makes for much easier debugging and maintenance. 21
- 22. Read books, magazines, blogs, Twitter feeds, and websites. If you want to go deeper into a subject, consider joining a mailing list or newsgroup. If you really want to get immersed in a technology, get hands on—write some code. 22