Getting 2 young boys to bed most nights is like trying to sweep up on a windy day, you feel like you’re chasing about trying to make something happen against the will of higher beings.
And then you have nights like last night that make up for all those others: following instructions without threats; only having to ask 4 or 5 times; interesting conversation and some unprompted affection.
Oh fatherhood, how amazing a ride it is.
This is a good video illustrating the problem with requirements documents:
Another problem with the process outlined in the video would be the lack of design involvement! :)
Jeff Croft recently wrote an article on what he calls the new layers of web development in which he makes the following key point:
“In short, I’m suggesting that the (X)HTML templates used for a website in today’s modern world are much more closely related to presentation than they are to content.”
This point is in reference to the 3 layers commonly used to describe web standards:
It’s a thought provoking read. In short though I’m not convinced that structure and content are the same. Content has structure and an interface has structure and (X)HTML code crosses both these areas. Jeff is suggesting that if (X)HTML is structure, that this structure is more for presentation than content. I agree that would be the case for a lot of web applications but not necessarily content sites. Even web applications have content that has structure (think headings, sub-headings, bullets etc).