From time to time people implement something that they want to use in a fire-and-forget fashion. Typically it is some non-critical service you want to notify. Sadly most people get this wrong since they don't understand what fire-and-forget means and instead fire blindly.
Xbox Live History - Part 2
The excellent first part of Xbox history has been followed up with a second part.
Bleeding HTTP status codes
Developing web services there is an anti-pattern that I often see slip through the cracks and that is when HTTP constructs bleed through abstraction layers.
Should bugs be user stories
One topic that seems to come up regularly when teams try to be adopt agile is how to deal with bugs. Since these teams typically give Scrum a try they feel the urge to get as many story points as possible so it is natural to wanting to give these bugs story points so you get some credit for them. IMHO that is a huge mistake.
Posted by cellfish at 06:03 No comments:
Subscribe to: Posts (Atom)