Home Page for 97 Things [97 Things] : Near-Time. 15 Tools to Help You Develop Faster Web Pages - Six Revisions. Response times, availability, and stability are vital factors to bear in mind when creating and maintaining a web application. If you’re concerned about your web pages’ speed or want to make sure you’re in tip-top shape before starting or launching a project, here’s a few useful, free tools to help you create and sustain high-performance web applications. I’ve tried to include a wide variety of tools that are easy to use, and have tried to keep them as OS and technology-independent as possible so that everyone can find a tool or two. 1. YSlow for Firebug YSlow grades a website’s performance based on the best practices for high performance web sites on the Yahoo! Developer Network. Each rule is given a letter grade (A through F) stating how you rank on certain aspects of front-end performance. 2.
Firebug is an essential browser-based web development tool for debugging, testing, and analyzing web pages. 3. 4. 5. mon.itor.us 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. More Tools and Related Resources. Classic Mistakes Enumerated. Some ineffective development practices have been chosen so often, by so many people, with such predictable, bad results that they deserve to be called "classic mistakes.
" Most of the mistakes have a seductive appeal. Do you need to rescue a project that's behind schedule? Add more people! Do you want to reduce your schedule? Schedule more aggressively! Developers, managers, and customers usually have good reasons for making the decisions they do, and the seductive appeal of the classic mistakes is part of the reason these mistakes have been made so often. This section enumerates three dozen classic mistakes. The common denominator in this list is that you won't necessarily get rapid development if you avoid the mistake, but you will definitely get slow development if you don't avoid it.
If some of these mistakes sound familiar, take heart. Some of the more significant mistakes are discussed in their own sections in other parts of this book. People #1: Undermined motivation. . #4: Heroics. Patrick Cauldwell's Blog - This I believe... the developer. I was trying to come up with a set of guiding principles as we've been using them on my current project, with an eye toward educating new developers being assigned to the project, so I wrote up a PPT deck for the purpose. Scott thought it would make a good, general purpose manifesto for any project, so here goes... These are my opinions based on experience and preference, YMMV. Much of this is common sense, some of it is arbitrary, but it's all stuff that I think is true. Our "guiding principles" Test Driven Development As much as possible, all of our code should be developed according to the TDD methodology. If we stick with it, we will always have confidence in the current build (i.e. that it really works).
Continuous Integration We want our build to produce something that looks as much as possible like a production deployment. To that end, our build deploys a real live system and runs "integration" tests against it. .NET XML Best Practices - Choosing an XML API. .NET XML Best Practices Part I: Choosing an XML API by Aaron Skonnard As someone who has spent the past several years learning and using the various XML APIs available throughout the industry, I can honestly say that the .NET implementations are the best I've seen in terms of productivity, efficiency, and extensibility.
The .NET XML framework provides support for all of the W3C-stamped XML specifications including: XML 1.0 Namespaces in XML DOM Level 2 XPath 1.0 XSLT 1.0 XML Schema All of the above have achieved the W3C Recommendation status, which means that the specifications have been approved by a majority of the consortium members. In addition to these W3C specifications, the .NET XML framework also provides support for several other XML-related technologies that don't share the same level of acceptance but which are quickly gaining mind-share as they continue to evolve: Streaming XML APIs (like SAX) This article is the first part of a three-part series on the .NET XML framework.