Comments on: Talk to the Hand http://www.soabloke.com/2008/11/11/talk-to-the-hand/ pushing soa up the slope (with a pointy stick) Tue, 30 Nov 2010 19:23:34 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Saul Caganoff http://www.soabloke.com/2008/11/11/talk-to-the-hand/comment-page-1/#comment-229 Saul Caganoff Fri, 21 Nov 2008 05:27:40 +0000 http://www.soabloke.com/2008/11/11/talk-to-the-hand/#comment-229 Yes and while we're bashing timesheet systems, I love the way people create "chargeable" activities and "unchargeable" activities as if the lowly data entry clerk (consultant whatever) understands what may or may not be chargeable under the work-order. Yes and while we’re bashing timesheet systems, I love the way people create “chargeable” activities and “unchargeable” activities as if the lowly data entry clerk (consultant whatever) understands what may or may not be chargeable under the work-order.

]]> By: Progressive Data Constraints | soabloke http://www.soabloke.com/2008/11/11/talk-to-the-hand/comment-page-1/#comment-228 Progressive Data Constraints | soabloke Fri, 21 Nov 2008 05:17:07 +0000 http://www.soabloke.com/2008/11/11/talk-to-the-hand/#comment-228 [...] ← Talk to the Hand [...] [...] ← Talk to the Hand [...]

]]> By: Lyndon http://www.soabloke.com/2008/11/11/talk-to-the-hand/comment-page-1/#comment-218 Lyndon Thu, 20 Nov 2008 04:13:37 +0000 http://www.soabloke.com/2008/11/11/talk-to-the-hand/#comment-218 Is there anyone who actually likes their current timesheeting system ? Also, I find it disappointing when 'managers' push off management tasks to technical people. What exactly is left for management to do when employees are logging their time at the micro level :-) Is there anyone who actually likes their current timesheeting system ?

Also, I find it disappointing when ‘managers’ push off management tasks to technical people. What exactly is left for management to do when employees are logging their time at the micro level :-)

]]> By: Richard Veryard http://www.soabloke.com/2008/11/11/talk-to-the-hand/comment-page-1/#comment-182 Richard Veryard Tue, 11 Nov 2008 09:55:54 +0000 http://www.soabloke.com/2008/11/11/talk-to-the-hand/#comment-182 Hi Saul I think the problem starts when your perfectly reasonable data gets labelled as "error" because it is inconsistent with your project manager's data. This happens in a lot of old bureaucratic systems because they are designed on the implicit (hierarchical, top-down) assumption that the manager (or systems designer) is always right and the worker (or data entry clerk) is always the one that gets things wrong. I prefer to label such inconsistencies as anomalies, because that doesn't imply anyone in particular being at fault. It would be crazy to have a business rule saying that anomalies are not allowed. Anomalies happen. What makes sense is to have a business rule saying how anomalies are recognized (i.e. what counts as an anomaly) and resolved (i.e. what options are available to whom). Then you never have to suspend the rule. It is just a different, more intelligent kind of rule. See also "Post Before Processing". Hi Saul

I think the problem starts when your perfectly reasonable data gets labelled as “error” because it is inconsistent with your project manager’s data. This happens in a lot of old bureaucratic systems because they are designed on the implicit (hierarchical, top-down) assumption that the manager (or systems designer) is always right and the worker (or data entry clerk) is always the one that gets things wrong.

I prefer to label such inconsistencies as anomalies, because that doesn’t imply anyone in particular being at fault.

It would be crazy to have a business rule saying that anomalies are not allowed. Anomalies happen. What makes sense is to have a business rule saying how anomalies are recognized (i.e. what counts as an anomaly) and resolved (i.e. what options are available to whom).

Then you never have to suspend the rule. It is just a different, more intelligent kind of rule.

See also “Post Before Processing”.

]]>