5 ms·
12 Steps to Writing Better Web Code
- Glowbox 15y agoGreat 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.
- kellysutton 15y agoI'm still having trouble wording Step 11, I'll admit. I often think that IDEs make the programmer a little too lazy (hear me out). If you're to the point where you can't remember where certain methods are defined, how something should be refactored, etc., your project probably got too bloated long ago. 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.
- glenngillen 15y agoI get autocompletion and finding of references in every editor I've used for at least the past decade. 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.
- unclebobmartin 15y agoGreat post. Love all the point except 11. You can have my IDE when you pry it out of my cold dead hand. -- Uncle Bob.
- threepointone 15y agoRegarding Step 6: Can you spin up ad-hoc development and staging environments with one command? Haaaaaave you met http://vagrantup.com/ http://vagrantup.com/ ?
- kellysutton 15y agoI have. It's pretty close to what you'd want, although I wouldn't mind paying for this as a service.