Thursday, May 27, 2010

Getting a Little Scary on the Korean Peninsula

Nearly lost among headline's of Lee DeWyze's American Idol victory and (albeit significant and important) news on the BP oil spill in the Gulf, is what I think is the biggest development on the Korean Peninsula I can remember.  Almost exactly two months ago the 1200t South Korean corvette Cheonan broke in two and sank after an explosion at her stern.  46 of her 104 man crew were killed.  An investigation was performed and despite hopes to the contrary, when the wreckage was raised the presence of remnants of a North Korean torpedo have confirmed that the Cheonan was deliberately sunk by hostile action (in this case suspected to have been a torpedo delivered by a North Korean Yeono-class minisub).

This is a big deal.  It's not a case of a bit of sabre-rattling gone a little too far such as the "Second Battle of Yeonpyeong."  In that battle, or the others like it, both sides were pushing each other's buttons in disputed waters and shooting broke out.  In this case, a DPRK minisub evidently stalked the Cheonan before the decision was made to fire on the ROK corvette.  At any time in history, between any two countries, this is reasonable cause for war-- and the two countries in question in this case are already at war (still).  The weirdest part is, I can't figure what the reasoning behind it was.  Usually Kim Jong Il seems to be perpetrating a game of brinkmanship wherein he shakes something up or pushes some agreement to the point of strain and then lets ROK or the US or whomever buy him off.  In this incident I can't see what he'd be looking to gain or why any usual gain would be worth the risk of such a bold move.  It begs the question, how monolithic is North Korea? I'm not sure which is more scary, a North Korea dominated by a generally unstable and seemingly batshit-crazy Kim Jong Il, or a North Korea being fought over by several extreme factions with competing goals and resources.  One angle that's been troubling my mind ever since it was reported that his health is failing, what if he's decided he should be the one to unify Korea and he feels time running out? 

From what I can gather from the news, South Koreans are angry.  And well they should be!  Can you imagine the response from the government and the populace if some one sank a US naval vessel?  That raises the question of a response.  In my opinion, if this was "brinkmanship," then you've already gone over the brink.  Appeasing Kim hasn't ever gotten us anywhere (though it did eventually lead to North Korea conducting two nuclear tests), and if he's resorting to overt military action to try to get whatever it is he wants then you certainly cannot countenance giving it to him.

Any military response would have to be exceuted very carefully.  I'm pretty confident that any general engagement between allied ROK and US forces versus an outdated, outmoded, and probably underfed DPRK military would be very one-sided.  Such an engagement needn't necessarily be "general," as you could, through any number of mechnaisms, probably sink a North Korean sub or five without it necessarily looking like it was you-- but a strategy like that could very easily and quickly escalate into a general engagement.  The problem with a general engagement, beyond the fact that war is almost always an undesirable outcome, is that Seoul is too close to the border with the North, and DPRK artillery assets could be used to bombard Seoul for at least a short while before it would be neutralized by allied response-- and that could cause lots of damage and many civilian casualties.

In any case, it's not a war yet, but I feel like there are a lot of scenarios that could turn it into one.  I hope it can be resolved via some reasonably peaceful approach that doesn't involve appeasement... But as long as an apparent madman like Kim Jong Il is in power, the North will be unpredictable and dangerous.

Monday, May 24, 2010

Link to something I found interesting about the oil spill in the Gulf

I thought this was pretty cool... Gizmodo's link to a CNN video about a few proposed solutions to cleaning up the oil disaster in the Gulf of Mexico.  That's really a disaster down there, and I'm struggling to see how we're practically going to fix it any time soon.

Triumphant Return from The Japans

I'm back, even if some of you didn't know I'd gone!  I took a business trip for my huge corporate employer to Japan over the last week.  I didn't have a lot of warning that I was going which is why I didn't post a "see ya's all later kinda blog" before heading out.  I even made a weak effort between the very long working days and numerous drinkings of Japanese beer to update the blog with an "I'm in Japan!!!!" kinda post, but was defeated by the intermittent wireless in the hotel.

Anyway, for what it's worth, I've been to Japan several times (including a year-long stint as a college exchange students), so it's a place I'm pretty familiar with... I like it there a lot and enjoy any chance to go that I can get.  This trip took me to Kobe, a small city on Shikoku, and a smaller industrial city near Nagoya (or maybe more accurately near Toyota).  I had been to Kobe (maybe known to you as the site of the devastating Great Hanshin Earthquake of 1995) once before during high school for a volleyball tournament, and I think that's probably when I started my love affair with things Japanese that resulted in my aforementioned college exchange there-- interestingly enough, I don't recall discussing the earthquake much or noticing a lot of damage or anything, even though I was there around one year later.  Kobe is a pretty cool city with some neat features (the Ijinkan-- barbarian houses-- left over from when Kobe was a trade port for early European traders are an example) and some cool places to hang out. 

I got to travel with three other guys, who all turned out to be decent travel companions.  Work travel in Japan was fairly fascinating as factories there are very different from our own.  There's a ton of automation, and the Japanese are able to cram a decent process into an unbelievably tiny space.  Supplier relationships are also executed in a very different way-- kind of paternalistic and definitely not arms length.  I think there's some things we could learn from each other.

This blog has been brought to you by mild jetlag, which saw me awake at ~4:30 AM and has given me a bit of extra time before work.

Thursday, May 6, 2010

Absurd, Hilarious and Pretty Scary Actually.

Amit sent me this MSN moneycentral article today at work as we discussed the huge crap the market took today.  So, in case you don't want to link over there, it's possible that the minipanic today (which included the largest intraday market decline since 1987) may have been triggered by a trader at Citigroup fat fingering a sell order.  The story goes that he hit "b" instead of "m" when trying to place a $16M sell order on Proctor & Gamble.  This caused P&G stock to plummet from $62/share to $37/share in practically no-time.  Luckily for P&G, NYSE has some built in technology to watch for something like this, and basically slowed down transactions of P&G for a short time (1-2 minutes) while things were sorted out.

I read this and laughed a lot... Immediately took the article around to coworkers to make fun of the poor SOB who happened to have a really really bad day at work today.  In all seriousness though, this may or may not have caused the intraday dip before the end-of-day rebound-- I'm guessing the Greek financial disaster also had something to say about it... But it's incredible to imagine that whatever system the poor Citigroup trader was using doesn't ask you to confirm a 16 BILLION dollar trade request.  I'd personally like to think better controls were in place since for at least short time major damage was done to at least one company and perhaps the market on the whole.