Skip to main content

The playbook: part 3

On October 11th, I wrote the playbook.

On November 13th, I wrote an update to that post.

Today is the final installment in the series. In the first two, I laid out how law enforcement officials use the system to a) kill minorities and b) ensure that the killers are not brought to justice. All while seeming to be doing their hardest to ensure justice. How do you do it?

Part 1: You intentionally sabotage your own case to the grand jury

Part 2: You put the victim on trial and leak information damaging to the case against the killer cop

Part 3 is the inevitable result that most killer cops are never indicted. In the Tamir Rice case, part 3 was dropped today: no indictment. Shocker, right? The DA did everything he could to ensure the grand jury would not indict.

Do black lives matter? I guess it depends on who you ask. To the cops and DAs in these very high profile cases that never indict or never get conviction because they deliberately over-charges and fails to get an indictment, I don't think black lives matter to them. And if you think "Well I am not black so what do I care"...you are solely mistaken. It's not going to stop at killing unarmed black people. Eventually they'll start killing white people in the same numbers, then maybe we'll get some movement on this issue.

This is a case where a 12-year old black boy was shot 2 seconds after cops arrive on the scene. Think about that. 2 seconds was all they gave him before shooting him to death even though they didn't have to drive up close to him. Even though there were civilians sitting closer to him without fear. This was in Ohio, not Fallujah. Even when our soldiers were in war zones, their rules of engagement was stricter than that. It was all caught on camera (no audio) and this DA could/would not get an indictment.

http://www.cnn.com/2015/12/28/us/tamir-rice-shooting/index.html

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…