I have had troubles writing unit tests for classes with a lot of dependencies. The reason for this is that the initialization of the state for my test code would look like: [Setup] public void Setup() {    stub1 = new Mock(); …   stub20 = new Mock();   mock = new Mock(); …// Setup mock and stub behavior   classToTest = new TypeOfClass( /a lot of code/); } This isn’t very maintainable. How do we make this easier to maintain? I’ve introduced a helper class that initializes most of the interfaces to stubs of [...]

I really recommend this. How do you read really complex css? How do you refactor complex css rules? The answers is: http://lesscss.org/ There is a port of this to .net. The site associated with it is down though. You might find the source on github however ;)

This program has helped me greatly. Not that I approve of IE6 or anything…http://www.my-debugbar.com/wiki/IETester/HomePage A former coworker told me about this tool:mankz: testing all versions of ie and almost enjoying it at the same time<div></div>

There shouldn’t be so much of a debate. I thought that ruby had better string handling until I found out that in python 3 the unicode issue is fixed. The languages are strikingly similar in some aspects, as they are different in others. There are lessons from each of these languages. In python I’ve seen beautiful and readable short programs. In ruby I’ve seen beautiful and well structured programs. I only know a little about each of these languages (but I think that I’ve been helped by learning them).

The jQuery approach is to avoid object orientation. This is an excellent way of avoiding bloat for small javascript hacks. If you’re starting to build javascript heavy applications then you might need to start organizing your code. The first thing you should learn is how to write jQuery plugins. Later on you will need to learn some simple object orientation. Here’s how: function TigerType(name){ var that = this; this.name = name; this.sound = "growl!"; this.roar = function(){ return that.sound; };[...]