The document provides tips for developing with WordPress. It recommends always learning through curiosity, not expecting to know everything, researching topics by Googling them and using WordPress resources like the codex. It suggests asking questions on support forums, following Twitter users for help, and looking at existing code and themes for examples. The document also advises testing features thoroughly, using debugging tools, and following a process of breaking problems down and crafting solutions.
3. How To Be A Hacker
• Curiosity - always be learning
4. How To Be A Hacker
• Curiosity - always be learning
• You aren’t expected to know everything
5. How To Be A Hacker
• Curiosity - always be learning
• You aren’t expected to know everything
• http://www.catb.org/esr/faqs/hacker-howto.html
6. How To Be A Hacker
• Curiosity - always be learning
• You aren’t expected to know everything
• http://www.catb.org/esr/faqs/hacker-howto.html
• http://samizdat.mines.edu/howto/HowToBeAProgrammer.html
19. Other People’s Code
• Look at code for examples and inspiration
• Use the default themes as guidance
20. Other People’s Code
• Look at code for examples and inspiration
• Use the default themes as guidance
• Search the plugin repository
21. Other People’s Code
• Look at code for examples and inspiration
• Use the default themes as guidance
• Search the plugin repository
• And then do it better!
34. Following a Process
• Names are important
• Test things first
• Debugging is your friend
35. Following a Process
• Names are important
• Test things first
• Debugging is your friend
• http://codex.wordpress.org/
Debugging_in_WordPress
36. Following a Process
• Names are important
• Test things first
• Debugging is your friend
• http://codex.wordpress.org/
Debugging_in_WordPress
• http://lmgtfy.com/?q=debugging+wordpress