Quotulatiousness

November 4, 2013

Law, the military, and the media

Filed under: Britain, Law, Military — Tags: , , , , — Nicholas @ 11:23

Sir Humphrey debunks a recent story in the Telegraph which makes a big deal about the British military hiring more lawyers at the same time as they are disbanding front-line units:

The Forces have always needed effective legal support, and arguably the tiny number of military lawyers provides an utterly vital capability. Its not just about the provision of support to people who understand the arcane intricacies of a military law system which is very complex, and very different to our normal law — though this is extremely important. It’s about the provision of people who bring a vital advisory role to Commanders on the ground, and the wider MOD.

[…]

Similarly, once the direct fighting is over, UK troops often find themselves operating in a very strange environment — one only has to look at Iraq in the aftermath of the initial war fighting phase to realise that its not a clear cut place to operate. The advice offered by in theatre legal personnel can often make a huge difference in helping commanders understand their freedom to operate, and what genuine constraints may affect them. For instance, on a single tour in Iraq, units may have found themselves conducting everything from searches, checking for IEDS, detaining known individuals through deliberate operations, and then engaging in combat — quite possibly in the same day. The requirement for modern troops to adapt very quickly to all manner of situations places a huge burden on them — it is important that they get the best possible guidance to know they are acting correctly. Certainly in this authors experience on both TELIC and HERRICK, the LEGAD advice was often one of the most critical parts of any potential operation.

The same lawyers provide vital services back home — in the Royal Navy for instance, there are a range of in house experts on the Law of the Sea, international maritime disputes and territorial waters and the like. This may sound questionable, but when the RN is daily conducting counter piracy and counter narcotics operations across the globe, or sailing in possible maritime flashpoints where different nations have very different interpretations of maritime boundaries, having a good legal understanding on hand of the art of the possible is absolutely vital.

“…almost half of all firearms discharges by police officers involve the shooting of a dog”

Filed under: Law, USA — Tags: , , , — Nicholas @ 10:33

Even if you’re not a dog lover, this story from Charles C.W. Cooke should get you upset:

A Google search for “dog shot by police officer” returns countless stories from across the United States. YouTube, too, is full of harrowing videos. There is even a website, the bluntly titled “Dogs That Cops Killed” blog, which seeks to “collect a few of the innumerable instances of police officers killing dogs” and to push back against the “wars on drugs, peace, and liberty.”

This unlovely trend has claimed the attention of Patrick Reasonover, a libertarian filmmaker in California who is currently raising money for a proposed documentary, Puppycide, through the crowdsourcing service Kickstarter. “We’re excited by this one,” Reasonover tells me, “because on so many issues — the War on Drugs, for example — it’s impossible to move the ball. You can feature the problems with the drug war, but there are so many embedded interests that one documentary isn’t really going to solve the problem. With this issue, however? We feel that it could.”

Around eight months ago, Reasonover began to notice the proliferation of online videos of police officers shooting dogs. “People were going nuts about it,” he recalls. “There were tons of views on these things. We had dogs and we were disturbed, so we thought we’d reach out and start contacting some of the victims.” In doing so, he quickly learned that the news reports and the published footage were only the beginning of the story. Because police departments don’t keep easily accessible records of dog shootings, it is hard to gauge the scale. A recent review of public records by the American Society for the Prevention of Cruelty to Animals concluded that almost half of all firearms discharges by police officers involve the shooting of a dog. But nobody really knows.

Indeed, even animal-rights activists aren’t fully aware of the numbers in their communities. “They would tell us that there were, say, five news stories on these dogs that got shot,” Reasonover says. “But through my digging and persistence I found out that actually, you know, 22 were shot and no one ever knew.” One thing led to another, and he discovered that “there is a set of people who are working across the nation, through lawsuits or legislation or appealing to the Justice Department.” As part of his project, Reasonover is hoping to file Freedom of Information Act requests in all major cities and jurisdictions in the U.S. and to get hold of all firearm-discharge records. From that, he hopes to assemble a better list.

It may make brutal reading. A recent lawsuit in Milwaukee filed by a woman whose dog was killed forced that city to compile its records. “They found that a dog was shot every seven days,” Reasonover says. “Just in Milwaukee.” And, unless something changes, the number will only continue to rise. “Over the course of the past forty or fifty years, dogs have moved from the barnyard to the back yard to the bedroom,” Ledy Vankavage, the senior legislative attorney at Best Friends Animal Society, has observed. In the meantime, the drug war has been ratcheted up, terrorism has become a pressing concern, and, as Radley Balko has so distressingly chronicled, the police have become increasingly militarized. “You have this recipe for these police entering our lives more and more and more,” Reasonover explains. “The dogs are there, and so they are killed.”

QotD: Software quality assurance

Filed under: Business, Government, Quotations, Technology — Tags: , , , — Nicholas @ 10:13

The fundamental purpose of testing—and, for that matter, of all software quality assurance (QA) deliverables and processes — is to tell you just what you’ve built and whether it does what you think it should do. This is essential, because you can’t inspect a software program the same way you can inspect a house or a car. You can’t touch it, you can’t walk around it, you can’t open the hood or the bedroom door to see what’s inside, you can’t take it out for spin. There are very few tangible or visible clues to the completeness and reliability of a software system — and so we have to rely on QA activities to tell us how well built the system is.

Furthermore, almost any software system developed nowadays for production is vastly more complex than a house or car — it’s more on the same order of complexity of a large petrochemical processing and storage facility, with thousands of possible interconnections, states, and processes. We would be (rightly) terrified if, say, Exxon build such a sprawling oil refining complex near our neighborhood and then started up production having only done a bare minimum of inspection, testing, and trial operations before, during and after construction, offering the explanation that they would wait until after the plant went into production and then handle problems as they crop up. Yet too often that’s just how large software development projects are run, even though the system in development may well be more complex (in terms of connections, processes, and possible states) than such a petrochemical factory. And while most inadequately tested software systems won’t spew pollutants, poison the neighborhood, catch fire, or explode, they can cripple corporate operations, lose vast sums of money, spark shareholder lawsuits, and open the corporation’s directors and officers to civil and even criminal liability (particularly with the advent of Sarbanes-Oxley).

And that presumes that the system can actually go into production. The software engineering literature and the trade press are replete with well-documented case studies of “software runaways”: large IT re-engineering or development projects that consume tens or hundreds of millions of dollars, or in a few spectacular (government) cases, billions of dollars, over a period of years, before grinding to a halt and being terminated without ever having put a usable, working system into production. So it’s important not to skimp on testing and the other QA-related activities.

Bruce F. Webster, “Obamacare and the Testing Gap”, And Still I Persist…, 2013-10-31

Vikings lose to Cowboys in last-minute TD drive

Filed under: Football — Tags: , , — Nicholas @ 09:01

The 27-23 result won’t surprise anyone who saw any Viking games earlier this season, although the score was closer than you (or the bookies) might have expected. With so many key players missing in Minnesota’s secondary, the Cowboys were supposed to keep the scoreboard numbers spinning, but the game was close right down to the final drive. It’s that final drive — where the Vikings couldn’t force a stop — that has been the signature of this year’s team.

With yesterday’s loss, the Vikings have now matched the worst start to a season in franchise history (1-7 was also the 1961 team’s opening record) — and will host Washington on Thursday night for an attempt to make it their worst all-time start. Adrian Peterson had his best performance in over a month, rushing for 140 yards and one touchdown on 25 carries. Christian Ponder’s last-gasp Hail Mary fell short, but his stats were respectable: 25 of 37 for 236 yards, one touchdown and one interception (82.7 QB rating) and a rushing TD of his own. Kicker Blair Walsh had his first career missed extra point after Peterson’s TD run, but the single point didn’t make any difference in the final result. It may have influenced the coaching decision to punt rather than attempting a 54-yard field goal later in the game (post-game, Leslie Frazier said that Walsh’s hamstring injury was the actual reason for not trying the long FG).

Over the course of the game, the Vikings lost even more players to injury, with right guard Phil Loadholt suffering a concussion, tight end Kyle Rudolph injuring his ankle on his touchdown reception, nose tackle Letroy Guion had a shoulder injury, and cornerback Xavier Rhodes being injured in a collision with linebacker Chad Greenway. Rhodes attempted to return to the game, but left after just one play.

At The Viking Age, Dan Zinski says this “has become a nightmare sort of season”:

For a minute it looked like the Vikings might pull off a stunning, draft-position-ruining upset over the Cowboys. The Vikings were trailing 20-17 early in the fourth when Adrian Peterson went into full-on beast mode, ripping off a 52-yard run to put Minnesota in scoring range, then hitting paydirt on an absolutely filthy tackler-dragging monster of an effort. By force of Peterson’s will alone the Vikes took a 23-20 lead, then watched their kicker Blair Walsh miss the extra point to keep the Cowboys within a field goal.

But momentum quickly swung back in the Vikings’ favor when on the ensuing Cowboys possession A.J. Jefferson picked off Tony Romo on a sideline pass. The Vikes had a chance to ice the game away there but came up short and elected to punt rather than have Blair Walsh try a 54-yard field goal. Was this the right move? Walsh has hit plenty of 50-plus yarders in his young career, but he’s also had hamstring problems, and he had just missed a PAT wide right. Leslie Frazier did not have faith in his young kicker to boot it through and rather than give the Cowboys good field position he elected to pin them.

In the end it wouldn’t matter. The Cowboys got the ball back with plenty of time and did what you were almost certain they would. Tony Romo worked the ball rather easily down the field against the Vikings’ defense and the Cowboys were finally able to stick it in when Romo hit Dwayne Harris on a 7-yard TD pass. The Vikes got the ball back in decent field position after a short kickoff but were unable to get into position and had to settle for a Christian Ponder final-second hail mary that fell well short.

The Daily Norseman‘s Eric Thompson says the Vikings played their best game of the season yesterday:

I know the headline sounds like it was something from The Onion Sports or Sports Pickle, but it’s sadly true.

When you think about it, Sunday’s game against the Cowboys was the best of both worlds for the two major camps of Vikings fans. On one hand, you have the #TankForTeddy, #MissionMariota, #SuckForTheDuck, and #JohhnyFootballGoesToMinnesota fans that know the season is already lost and don’t want any pesky wins screwing up our 2014 draft position. They were satisfied because the Vikings lost again. On the other hand you have the fans that can’t stand the team laying down and getting blown out every week. They were satisfied because the Vikings actually played pretty well against a division leader on the road.

I get that many Vikings fans that don’t mind the losses since it could eventually lead to a better future for the team: better draft picks, new coaches, an overhaul of a largely inept roster. But you guys realize that we’re only halfway through the season, right? Are you sure that you can endure eight more weeks of this crap? Because I certainly wouldn’t mind a win or two sprinkled in with all the misery.

Living in a Surveillance State: Mikko Hypponen at TEDxBrussels

Filed under: Liberty, Technology, USA — Tags: , , , , — Nicholas @ 00:01

Powered by WordPress