12 Steps to Writing Better Web Code
kellysutton.tumblr.com
12 Steps to Writing Better Web Code
1–7 of 7 posts
Re: 12 Steps to Writing Better Web Code
#2The only thing I'm not too sure about is step 11, discouraging of IDEs. I do agree with your point that one should not depend on a IDE. However, IDEs can give you autocompletion, easy refactoring, finding references etcetera. Personally, I find some of these features invaluable.
Re: 12 Steps to Writing Better Web Code
#3Great post and most of these steps are really helpful. The only thing I'm not too sure about is step 11, discouraging of IDEs. I do agree with your point that one should not depend on a IDE. However, IDEs can give you autocompletion, easy refactoring, finding references etcetera. Personally, I find some of these features invaluable.
By forcing you to keep much of the project in human memory, services, in the world of the web, are encouraged to get spun off much sooner.
Re: 12 Steps to Writing Better Web Code
#4Great post and most of these steps are really helpful. The only thing I'm not too sure about is step 11, discouraging of IDEs. I do agree with your point that one should not depend on a IDE. However, IDEs can give you autocompletion, easy refactoring, finding references etcetera. Personally, I find some of these features invaluable.
As for easy refactoring, I definitely found it useful when I was doing C#. In hindsight I think it became a bit of a crutch and prevented me from properly re-considering how I should approach the problem and instead ended up with essentially the same but neater code.
Re: 12 Steps to Writing Better Web Code
#5You can have my IDE when you pry it out of my cold dead hand. -- Uncle Bob.
Re: 12 Steps to Writing Better Web Code
#6Haaaaaave you met http://vagrantup.com/ ?
Re: 12 Steps to Writing Better Web Code
#7Regarding Step 6: Can you spin up ad-hoc development and staging environments with one command? Haaaaaave you met http://vagrantup.com/ ?