Great summary piece at MSNBC about the recent NYT editorial supporting clemency for Edward Snowden. They correctly call out the double standard:
Since the beginning, the Obama administration has adhered to a double-standard when it comes to violations of the law by national security officials, punishing those that arouse the ire of the national security establishment while looking the other way when the law is broken in pursuit of their goals.
Of course this isn’t just Obama, it’s all administrations. If Obama’s failures here were surprising to you, they shouldn’t have been:
Before even taking office, Obama indicated publicly that he was unwilling to look into prosecution of Bush-era officials for their role in crafting torturous interrogation policies, saying he would look into whether “someone had blatantly broken the law” but that he possessed ”a belief that we need to look forward as opposed to looking backwards.”
Maybe occupants of the Oval Office eschew prosecution of their predecessors as some kind of insurance against the same by their successors — a kind of dirty political pay-it-forward. Nonpartisan history/political podcaster Dan Carlin has been talking about this for years. I highly recommend listening to his show.
No sooner had I written about a presentation that’s been making the rounds and how it might affect our teams at Red Hat, I find this piece on DZone. Super relevant, especially since we often occasionally use the scrum-of-scrums practice.
From the slides:
Make communication across context boundaries explicit. Use integrating teams to agree how to handle the interface and integration between systems. Integrating teams should also agree on and write acceptance tests that confirm integration across boundaries. (Emphasis mine)
Kris Gale from Yammer posted a great narrative about how he believes the traditional engineering organization is dead. In particular he calls out the failed strategy of having managers orchestrate multiple teams who are aligned along technical ownership:
If you imagine a typical medium to large engineering organization chart, you might have a front-end team, a back-end team, and potentially a “middleware” team. Those teams own their code bases; each one has a proprietary manager and those managers report up to some boss. The point is that the organization usually matches the code’s architecture. When it comes time to do work, the managers at the top have to make decisions about what’s being built before they can break up and delegate work. You then have questions like “What is the backend team going to do?” and “How does that interface with the front-end team?”
I agree with this notion but I think his definition of “managers at the top” may differ from mine – nowhere in my history has a “top level manager” orchestrated what the technical teams work on. They might set project priority but nothing more granular than that. It’s possible that I’m just quibbling about definitions. So be it.
I didn’t always think this way. My peers and I have been talking for some time about re-organizing the engineering teams we manage in just the way Gale describes. My objection to it has always been that when you strew responsibility for a single application tier or technology across teams, you wind up with lousy code — inconsistent, unreadable and with potential duplication. I’ve advocated for keeping code that lives within a certain technical domain owned by experts in that domain.
As it has played out, we have struggled a lot with driving features into our products when they concern two, three or more work streams. So I believe we’ll be taking a similar tack to that which Gale proposes. The cost of adding features due to this overhead is not trivial.
I’ll try to take some time and post my thoughts as we adapt.
Surprising many and relieving others, Barack Obama won a second term last night in a pretty big way. This is my ants-at-a-picnic view of the situation.
Things will continue to get better, little by little, as they always do, even as politicians try as they may to break them more. More people will find jobs because this is what we do: we work hard and provide for ourselves and our families (most of us).
The financial situation will get better because there is no choice in the matter. But one thing is for certain: no matter how measurably better things are, republicans will surely disapprove and continue to obstruct and bash the president at every turn. The media will stoke the fires of resentment and disagreement because we buy it up with our precious attention. Because this is what we do: we tear down those with whom we disagree without understanding.
Obama will continue to wage quiet warfare in who-knows-how many countries, killing who-knows-how many brown people whose families will vow to destroy us. He will continue to erode our civil liberties further and further whether it be wiretapping, spying, detention or assassination. And his supporters will be silent, even though these actions are in stark contrast to their supposed ethos. Because this is what we do: we unconditionally support the person who lives in a shell of that with which we want to identify.
And the rest of us will sit in waiting until one day when we might possibly have a way to express our disgust at all of it.
I’ve written before about what I think is wrong with our financial system. David Stockman’s piece takes aim at Mitt Romney and in the process provides one of the best summaries of Wall Street I’ve ever read:
That is the modus operandi of the leveraged-buyout business, and in an honest free-market economy, there wouldn’t be much scope for it because it creates little of economic value. But we have a rigged system—a regime of crony capitalism—where the tax code heavily favors debt and capital gains, and the central bank purposefully enables rampant speculation by propping up the price of financial assets and battering down the cost of leveraged finance.
Check out the whole article.
I just watch Khan Academy founder Salman Khan’s excellent talk from TED 2011. I’m inspired by this kind of thinking and equally entertained by his delivery. He describes a new approach to classroom interaction that arose when he began posting YouTube vidoes of his tutoring sessions to help out his cousins. Specifically, the notion that he’d ask the students to watch the lectures at home and then do what would normally be considered homework while in the classroom:
I want to pause here for a second, because there’s a couple of interesting things. One, when those teachers are doing that, there’s the obvious benefit — the benefit that now their students can enjoy the videos in the way that my cousins did. They can pause, repeat at their own pace, at their own time. But the more interesting thing is — and this is the unintuitive thing when you talk about technology in the classroom — by removing the one-size-fits-all lecture from the classroom and letting students have a self-paced lecture at home, and then when you go to the classroom, letting them do work, having the teacher walk around, having the peers actually be able to interact with each other, these teachers have used technology to humanize the classroom. They took a fundamentally dehumanizing experience — 30 kids with their fingers on their lips, not allowed to interact with each other. A teacher, no matter how good, has to give this one-size-fits-all lecture to 30 students — blank faces, slightly antagonistic — and now it’s a human experience. Now they’re actually interacting with each other.
Brilliant. I highly recommend watching the whole video.
What follows is my ice breaker speech, project #1 in the Toastmasters Competent Communicator guide. I delivered it today at the Red Hat Open Voice Toastmasters chapter in Raleigh, NC.
Presentation outline and notes/references for my Traiangle Java User’s Group presentation given on April 18, 2011. The slides used during the presentation are merely an instrument for me as the presenter; they aren’t available for download. Below is the rough outline I (kinda) followed and at the bottom are references and helpful links. Feel free to leave any and all candid feedback in the comments. Thanks for attending! Continue reading