IMO, "don't hardcode things" is a general good practice and a good 
suggestion but it's becoming clear to me that if you want to make good use 
of AJAX you need to start with a clear vision of what you want your user 
interface to look like.    
     
 "Don't hardcode things" is a substitute for requirements analysis for 
people who lack that sort of clear vision. Yes, if you go through your 
code and dehardcode things, you may end up with a more flexible codebase 
and in some cases a more well factored codebase.    
   
   
 But you may end up nowhere closer to whatever your goals are, if your 
goals are to use AJAX. You'll end up with flexibility in places that 
doesn't help towards your goal.  
  

Reply via email to