Citi’s Creator, Sandy Weill, Alone With His Regrets - NYTimes.com

On that day, April 18, 2006, Citi’s share price was $48.48. After studying the photo for a few moments, Mr. Weill says quietly, “I thought the company was impregnable.”

He knows now, of course, that he was wrong.

Over the last two years, Mr. Weill has watched Citi — a company he built brick by brick during the final act of a 50-year career — nearly fall apart. Although every taxpayer in the country has paid for Citi’s outsize mistakes, for Mr. Weill the bank’s myriad woes are a commentary on his life’s work.

...

“The dream, the mirage has always been the global supermarket, but the reality is that it was a shopping mall,” says Chris Whalen, editor of The Institutional Risk Analyst, of Citi’s evolution over the last decade. “You can talk about synergies all day long. It never happened.”

US Patent Office tightens the screws on software patents

In its decision, the BPAI announced a new two-pronged test for determining whether an invention involving a mathematical algorithm would be eligible for patent protection. First, the invention must be "limited to a tangible practical application" and result "in a real-world use." Second, it must be "limited so as to not encompass substantially all practical applications of the mathematical algorithm" in all fields or even in "only one field.

The Best and the Worst Tech of the Decade - O'Reilly Radar

SOAP was a particularly egregious failure, because it was sold so heavily as the final solution to the interoperatibility problem. The catch, of course, was that no two vendors implemented the stack quite the same way, with the result that getting a .NET SOAP client to talk to a Java server could be a nightmare. Add in poorly spec'd out components such as web service security, and SOAP became useless in many cases. And the WSDL files that define SOAP endpoints are unreadable and impossible to generate by hand (well, not impossible, but unpleasant in the extreme.)

Yes, SOAP is at the TOP of the Worst list...

Customers are always right, except when they are wrong

We noticed once we added the $9 plan, we started getting more tech support requests. Customers who typically pay us $49 and $99 tend to have less questions and are usually more satisfied with our product. On the other hand, customers on the $9 plan tend to ask a more questions and generally aren’t as satisfied as the higher paying customers.

Essentially, you don't always make it up in volume...

Tech Decisions: Aggressive IT Spending Predicted for P&C Carriers

In looking at the top drivers for technology spending, Furtado reported business growth was cited as the top driver by 66 percent of respondents. This was followed by both business process optimization and cost containment/expense reduction, each of which was cited by 56 percent of respondents.

“These drivers reflect the need to strengthen processes and stay competitive,” said Furtado

Insurance & Technology: Insurers Warm to Flexible Technology Architecture

Some choice quotes from the above named article...  You can find it here
 
O'Connell suggests. "Senior business executives are sitting down and asking questions about the architecture that this new platform will be built on and asking for assurances that three years down the road we will be able to reuse the platform and architectural components and be able to give them the flexibility they need," O'Connell says. "They really want to understand." 

The former Hartford Life CIO says that in the past the company found value in the flexibility granted by letting the company's various businesses go their own ways with regard to technology decisions. But even though flexibility may be more important than ever, he adds, as the businesses have matured scale and efficiency have become more important.

suggests Infosys' Mohan. "Technology modernization cannot be justified on the basis of technical merit alone," he says. "There has to be significant business upside for modernizing or re-architecting to be approved." 
 
Hartford P&C CTO Kim identifies four layers of enterprise IT that the committee considers: infrastructure, platforms, applications and business architecture. "The trick is understanding which of those layers is appropriate for different services. In some cases it's a shared platform, but the application might differ between life and P&C," he explains. "That's the art -- not science -- that we're grappling with right now."