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

Belated Quotes: Jeff Jarvis kills on this week in google TWIG 13

Here are a few belated quotes from TWIG 13/

Jeff Jarvis: 07:55 - "Say what you want, a Microsoft phone will never ever make sense to a human being...  It's impossible! No matter how many good apps
youvput on an Microsoft OS it will not... I can't find them! I can't get to them! I have two or three Microsoft OS phones and they're dreadful!"

Jeff Jarvis: 13:20 - "I'm glad to have it there but there are two things that bother me about the announcement. (Bing/Google Twitter Search).  The first is that Twitter/Facebook/Bing are selling content that is not theirs, it's ours...  If Twitter were of the cloud,  there would be an API and you could just search it... There wouldn't be a case of making a deal like that, with one person and not the other.  Though Ev has said that he intends to make this non-competitive and open which I assume he'll do.  The second thing that bothers me is it sets a terrible precedent. Because these ah... I'll say it, these idiot newspaper people... will now say 'You paid twitter so you should pay us' .  Of course it's entirely different, but it's going to confuse the heck out of  their little brains!"

Jeff Jarvis: 19:20 - "Twitter is the first company built for the post 'page' Internet... They just don't know what it means yet."

Quotes: SE Radio 148 - Software Archeology w/ Dave Thomas

The Teutonic Technology podcast that's always worth a listen...

Dave Thomas: 2:40 - "Everyone spends all their time trying to figure out how write code... Very few people spend any time at all working out how best to read code, and that's a really big mistake. Because if you think about it because the average software developer probably spends 20% of their time writing code and the rest of the time reading it. and yet the training is totally the other way around..."

Dave Thomas: 4:50 - "If you think about any other creative profession, ... a writer or a painter. You certainly don't just sit there and write or paint. If you're a writing student, you'll be reading other peoples work. In fact most of your work will be reading the great classics, reading what other people of done and seeing how other people have constructed books... If you're a painter, you'll spend time studying other painters and yet if you're a software developer, you never read anybody else's code. You spend your entire time writing your own, which is an incredibly arrogant approach to the profession."

Dave Thomas: 25:10 - "If you are doing serious code archeology, you owe it to yourself to learn the command line, because you can not do it as effectively inside an IDE."

Dave Thomas: 27:00 - "You could always spot a team that has bought a copy of "Design Patterns" because they can't write "Hello Word" without three decorators a visitor and ... Alot of people misunderstood what patterns were. Everybody thought patterns were like software Lego, and I'll construct my software by building it out of a whole bunch of patterns and that totally misses the point. Patterns are not a construction device, they are a way of dealing with common issues when you're writing code. They are idioms, they are not designs."