This is MarkWSchumann's Typepad Profile.
Join Typepad and start following MarkWSchumann's activity
MarkWSchumann
Recent Activity
It sounds as though Fox is making a procedural argument against post-and-forfeit.
But what about the validity of the arrest ab initio? Judicial economy is a poor argument for speedy processing of a bogus arrest. (Or put another way, nothing's more economical than leaving the guy alone.)
I'm suspicious of anything that justifies many arrests but few prosecutions. Don't you think DC police (and others) are abusing the charge of disorderly conduct? Do the officers actually not understand the elements or do they not care because there is no realistic penalty for overstepping? In that vein, why are there not more complaints of false arrest?
Sutherland Lawyer Wants D.C. to Pay Up After Arrest
When Washington attorney Hamilton "Phil" Fox III was arrested in late 2008 on a charge of disorderly conduct after challenging a police order to move his car, he paid $35 and was released from a police station. Fox, a white-collar criminal defense partner in the Washington office of Sutherland As...
Very interesting perspective. It sounds a little bit like biodiversity; you're better off having a variety of solutions, even at the cost of sometimes not applying the very best one. Because the diversity itself is part of the solution too.
I Follow My Rules, You Follow Yours
It's ok when I follow my own rules, and when you follow yours. As long as we agree on the value of each other's output. In software projects the behavior of team members is guided by practices. Practices on how to document requirements, how to estimate work, how to commit source code, how to w...
If by "here" you mean this team with this mission, it's certainly possible for a given software method to not work "here."
E.g., the method is RUP but I have three very sharp C++ developers. Overkill.
E.g., the method is TDD but the environment simply doesn't support testing hooks.
E.g., the method is any kind of Agile but the management is not willing to yield any degree of control.
The contrary assertion to "this method won't work here" must be "this method will work here," and your claim is global. I don't think you can support "this method will work everywhere" though.
This Software Method Doesn’t Work Here
I’ve never heard a good cook say, “this recipe doesn’t work here.” What if a cook follows a recipe to the letter, and it turns out that the result is not what the cook expected? Can he say that the recipe failed to “work”? A recipe is just piece of text, nothing more. You cannot say “The reci...
I'm just saying I wish I happened upon this about three months ago.
A huge advantage of smaller user stories is that they move through the Kanban (or other workflow) so much more quickly. That avoids deadlocking and keeps team members usefully busy more of the time.
It's that "seamless flow of small, valuable changes" Matthias talks about. It really is better.
Slicing and Dicing Epic User Stories
Today I ran a workshop ideas to explore how to slice epic-sized user stories at Redgate in Cambridge. I'm going to share some of what we covered with you in this blog. In my work as an agile coach, I find many teams applying Scrum are puzzled about user stories. I guess one reason is that this t...
MarkWSchumann is now following The Typepad Team
Sep 18, 2010
Subscribe to MarkWSchumann’s Recent Activity