clbusts in Php y otras yerbas proposes an idea for a new tool that might help users and developers reach understanding more quickly. When thinking about a new piece of software (or even an old one like the inevitable "text editor" that is such a favorite for programmers), we list all the characteristics that the software should have. Each user then assigns a number to each characteristic representing how important the characteristic is to them. After counting the votes, we have the profile of the program that meets most users' wishes.
Joserra in Najaraba.com posts an extract from his MBA thesis where he discusses how a company should be organized internally to deliver open source software.
Cesar Tardaguila in design-nation found a link to Google Earth via the site Error500. He complains that the requirements for running Google Earth are quite high and written in a language that most users would not understand.
JorgeBec in Ingenieria de Software posts a link to the archive of the manuscripts of Edsger W. Dijkstra. He was an important figure in the early days of computing, and wrote on subjects like algorithm design, programming languages, program design, operating systems, distributed processing, formal specification and verification and the design of mathematical arguments.
Patxi Echarte in EsLoMas.com releases a class that allows a PHP program to retrieve all kinds of information about the HTTP request of each attempt to access a page. The article gives a full listing of each item of data and its meaning, and the download has an example showing how it can be used.
jasm in chochurro muses on the various argumements for and against normalization in data bases. Excessive normalization leads to increased complexity and reduced performance as each item is retrieved from its table. However inadequate normalization leads to duplication of information. In the design, attention should be paid to those items that are expected to change frequently and to those that are not, and the consequences of such changes. He gives an example of an invoice where the address of the customer is not likely to change often but where such a change may or may not be important depending on the local regulations.
Cesar Tardaguila in design-nation presents a dice application for the Mac which is available for download. The article describes step by step how to develop a Mac OSX application and adds to the tutorial in the Apple Developer Connection.
![[Image]](../../Images/MadeWithCityDesk.gif){kind=small}