I’ve been really busy lately. My mail keeps accumulating and I want to write more about Monorail and ASP.NET. Soon.

General

• How to Write Killer Blog Posts and More Compelling Comments – The name speaks for itself. Not a development link, but I think many people can benefit from at least scanning it.

Tools

• Saltstorm – Cool JavaScript compression utility. I’m sure there are many similar tools, but this is professionally done and well documented.
• Ultimate Developer and Power User Tool List – A great list of tools that every developer and most of power users should be at least aware of.

Web development

• Efficient JavaScript code - Writing efficient JavaScript code can be a complex task. This article will help you to know the cost (in terms of memory, execution time, etc.) of various things in JavaScript. My only concern is that it’s written from Opera's perspective, which is not as widely used as IE or Mozilla and so the applicability of the article diminishes.
• Data persistence in IE – Overview of how to use IE DHTML Behaviors (proprietary Microsoft extension for IE to ease control creation) to persist user data (such as view or control state).
• Understanding and Solving Internet Explorer Leak Patterns – A great article from Microsoft on what can cause memory leaks in IE. An interesting read providing good insight into the problems I’m trying to solve with my UI project.
• Six JavaScript features we do not need any longer – Discussion on six JavaScript features that author think should be avoided in JavaScript development (as well as thrown out in the future versions of JS). Mostly I agree, but I don’t think "href="javascript: …", onclick="javascript:" can be thrown out yet. Not until Microsoft fixes the problem with IE only supporting “:hover” CSS pseudo-class for the anchors (<a></a>). Using JavaScript here can prevent anchors from navigating away from the page ("href=”javascript:void(0)"). Using anchors is inappropriate in many cases (which doesn't stop most developers, including me, from doing it), but it can really simplify life sometimes.
• W3C DOM vs. innerHTML – Another article on JavaScript performance. In this case, two ways to manipulate the page are compared and apparently, “innerHTML” wins in most of the cases. Still DOM is often more convenient. In most cases, the difference should not be noticeable, but it’s nice to know what to look at if JavaScript seems to take too long to execute. Don’t forget that it’s also possible to use various JavaScript profilers, such as Mozilla Venkman.
• Object Hierarchy and Inheritance in JavaScript – In-depth JavaScript OO capabilities overview. Most certainly, you will learn something knew or recall something you’ve forgotten about what JavaScript is capable of.
• Design for future: workarounds vs. hacks – All web developers who has to work with CSS sooner or later discover inconsistencies in how browsers handle CSS as well as run into CSS limitations. This article is a good starting point to understanding hacks and workarounds possible in CSS, how they can help and when they’re appropriate to use.