Nov 08 2007
50 Ways to Become a Better Web Developer
In the spirit of liquidcity’s 50 Ways to Become a Better Designer, here are 50 ways to become a better web developer:
- Read Alertbox
- Stay current on new startups: Read A VC
- Occasionally read A List Apart (when it’s not being too pretentious)
- Always think about the user all the time
- Write code that fails well
- Avoid feature creep
- Either fix the first bug you open or move it along somehow, don’t just ignore it
Catchgracefully deal with SQL errors in your database wrapper functions- Write database wrapper functions
- Write a config file that automatically adapts to the server it’s on: development, staging or production
- Don’t use frames
- Fix bugs first
- Comment your code (on the why, not the what)
- Don’t burden the user
- Don’t create widgets
- Don’t break the back button
- Don’t use bits as arguments for methods
- Write and use stored procedures
- Resist version rot
- Make everyone at work use a wiki to store usernames and passwords for projects
- Step away from the computer for a few minutes (don’t go read Slashdot, actually step away)
- Actually build something with a fun JS platform like Dojo or jQuery
- Build something using Django
- Don’t work on a social networking startup
- Learn LISP
- Read Paul Graham‘s essays
- Write a spec first
- Be precise; details matter
- Be succinct
- Make it beautifully perfect
- Use FogBugz to track your bugs
- If you find yourself saying theoretically it should work fine – it won’t
- Always test your code
- Seriously, always test your code
- Have someone else test your code
- Have someone else review your code
- Don’t major in computer science
- Use two big monitors
- Use a fast computer
- Organize your code
- In pretty much all things short successful iterations work best (and are more efficient)
- Test it in Firefox and IE
- Just accept that the IE team won’t get IT right and deal with it
- Benchmark and focus on performance… after the first prototype
- Play XBox 360 (alternative usage of your hands will ease the strain)
- Use Firebug with Firefox
- Use the web developer toolbar with Firefox
- Validate all user input
- Read the spec the whole way through before you start
- Always have a goal you know exactly how to meet
LISP, nice…