Skip to main content

What we've learnt Extreme Interrogation Techniques

  • It is torture. Torture, like a rose, by any other name is still torture
  • We all knew it was going on and we all turned a blind eye
  • It was systemic. It wasn't just a wink-and-nod kind of thing. There were memos and all sorts of legal instruments to give the doers legal authorization
  • You know there's something shady going to when memos are being destroyed. That demonstrates an awareness of wrongdoing.
  • We are better than that. If we have to resort to the methods of our enemies, then what are we fighting for?
  • "Warrantless wiretapping" is illegal. Period.
  • The funny thing is history is replete with warnings about the fallacy of trading freedom for security.
  • If this was done by a third world country, you bet the president of that country will be charged with war crimes.
  • Eventually, the period of Bush's presidency from 9/12/2001 till he left will be known as the dark days in American history. That along with things like segregation and race inequality.
On the question of whether or not these techniques ("techniques" is so clinical a term for something so God-awful) worked: really what does it matter whether or not they worked! The question is whether they were legal under US constitution. No reasonable person will try to make a case that slavery worked; or that searching a defendant's property without a warrant works. We know these things aren't allowed under the constitution so the question of whether or not they work is a non-starter. 

Bush people will like us to believe these techniques are what kepts up safe from 2002 till now. But is that the best we can do? Is that the lofty standard to which America wants to be held? 

Reblog this post [with Zemanta]

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.…

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…

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…