Please banish the use of the word “Requirements” from your software development lexicon. Immediately.
For many software teams the requirements document is the king of documents.
You know the routine. The software team works with the customer (or customer proxy) to put together a “complete” list of “requirements”. Once that is done, the team writes the software implementing the requirements and voila! the project is done.
Or maybe not.
Almost on queue, Twitter has recently done (twice!) what I’ve been thinking about lately. They have removed features.
Removing features is very tricky and fraught with problems, even if those features are used by very few people.
So the twitter changed their notification emails for when someone follows you. And they are definitely an improvement over the old notifications.
But they are broken.
I’ve read several articles talking about the “richer, HTML version” of the email. Richer? What year is it? Formatting doesn’t make something “rich”, data does.
Data is rich, markup is lame.
Often reading about economics, foraging for and growing food, playing silent sports, and making software. Also, ping pong!
Often playing with his 7 year old daughter. Mark is a avid runner, into martial arts, and philosophy.
Recent Comments