All Tags // performance
Anyone that's been building web applications (or doing anything else, for that matter) for any length of time has undoubtedly established a few operating principles that drive the way they work and the deliverables they produce. I have mine. Not too long ago, I sat down and made an effort to articulate the principles (well, at least the big ones) that drive my work and, after some thought, decided to publish them here. I'd be interested in hearing how others apply (or avoid) the principles that I follow.
- Keep It Simple, Stupid
- Separate Presentation from Content
- Separate Content from Behavior
- Prefer Extensibility to Performance
- Prefer Readability to Perforance
- Prefer Simplicity to Flexibility
- Less First, Then More
About a year ago I wrote a feed aggregator for a content management product. In doing so, I ran into a number of issues - some big, some small - that had me banging my head against a wall until i finally tracked them down. This morning, Bob Imperial asked a question on the CF-Talk mailing list related to one of those topics. I answered his question and went to work tracking down another, similar question that I knew I had responded to in the past. I thought it was the same question so my intent was to blog the solution in case anyone else was having the same problem.
