Paul Boag covers strategies for working better with design clients.

The Dependency Inversion Principle relates to the stability and reusability of higher-level components within an application. The principle states:

A. High-level modules should not depend on low-level modules. Both should depend on abstractions.
B. Abstractions should not depend upon details. Details should depend upon abstractions.

Read more here.

"Wherever the music comes from, if there is no focus behind it then it's just noise".
Electronic Beats Slices Feature about Detroit legend Derrick May.
Taken from Slices Issue 4-11.

In my opinion that principle is really important and stays in the fundamentals of software design.

In the context of the Single Responsibility Principle (SRP) we define a responsibility to be "a reason for change." If you can think of more than one motive for changing a class, then that class has more than one responsibility. This is sometimes hard to see.

Read more about this principle here.

Are you wondering what you can do with Canvas and WebGL. Check http://mrdoob.github.com/three.js/ to find out.

https://www.mugeda.com/animation/edit/1263

That's a great article by Robert C. Martin. It's one of those articles that really may change something in your programming. The principle is called Open-Closed and it says:

SOFTWARE ENTITIES (CLASSES, MODULES, FUNCTIONS, ETC.) SHOULD BE OPEN FOR EXTENSION, BUT CLOSED FOR MODIFICATION.

More about that here.

Just a great article. Period! http://anarchycreek.com/2009/05/26/how-tdd-and-pairing-increase-production/

I had a lot of work these days and didn't have time to blog here, but I think that the tips in this article are very useful. The number of Facebook applications is increasing every day. We all know that the testing (debugging) of our code is really important. That's why I decided to share my experience in this area.