Amazon.com has invested in the start-up behind folksonomy project 43 Things. Another company, called 37 Signals …

-Conduct Creative Code Reviews.

Code reviews can be formal or informal, and they can be great even if you’re a single-person team. I’ve had great luck read code printouts in all sorts of odd situations – in the pool, at the beach. Give it a shot. Try using markers and hacking the printouts all up. Try pasting all your code on the walls of a room, and assign a section of a wall to each team member.

A software slipup in Microsoft’s latest update to Office 2000 results in the application repeatedly asking some customers to register the program.

Most programmers do not write tests. We all know that we should write them, but for whatever reason, most of us don’t. This is unfortunate, because testing is the most powerful tool we know of to improve software quality. Tests reduce bugs, provide accurate documentation, and improve design.

This is for the rest of you too!

I had attempted to write this article once before, but I did not like what I wrote and scrapped it. I don’t see articles like this and was hesitant to express my comments. Perhaps all publishers can view my position in a similar manner when it comes to those little things that bug us.