|Links for 2005-3-22
||[Mar. 23rd, 2005|04:09 am]
Building Adaptable Systems:
Reversible design decisions, the cost of change curve, going beyond the requirements, and making systems configurable.|
The importance of programming defensively against your own and other's mistakes, of crashing near the cause, and understanding the proper use assertions.
Programming Close to the Domain:
The benefits of programming in a language close to the business domain.
Orthogonality and the DRY Principle:
The importance of keeping your system orthogonal, and the real meaning the DRY, or Don't Repeat Yourself, principle.
Programming is Gardening, not Engineering:
A gardening metaphor for software development, the reasons coding is not mechanical, and the stratification of development jobs.
Good Enough Software:
The myth of bug-free software, the importance of specifying level of quality as a system requirement, and the need for every team member to inject quality throughout the development cycle.
Abstraction and Detail:
An approach to design in which details are pulled out of the code and stored as metadata
Plain Text and XML:
Dave Thomas and Andy Hunt discuss the value of storing persistent data in plain text and the ways they feel XML is being misused.
Tracer Bullets and Prototypes:
The importance of getting feedback during development by firing tracer bullets and building
GNOME Desktop News
HowTo: RSS Feed State:
Getting most out of your RSS feeds.
The best way to organize your room:
Some simple but effective advice on how to get your space in order.
The Pragmatic Programmers:
Homepage for the book series with many articles and links.
but she’s a girl…:
UK Geek Girl blogger.