Posts in "tech"

[audio cote.files.wordpress.com/2014/08/u…_009.mp3]

underdevpodcast:

Summary

Bill and Coté discuss trying to explain DevOps, DevOps metrics, and the processes used by designers vs. software developers vs. management consultants vs. wedding planners. We also go over the recently US Digital Services Playbook, which looks pretty cool actually.

Subscribe to the feed: http://feeds.feedburner.com/UnderDevPodcast

Your friends @cote and @BillHiggins

DevOps, what is it?

IBM Design, Process

  • Bill now works in the IBM Design Group now.
  • What are “Design” people like? Ideation, post-it notes, user-centric thinking.
  • Three schools of process: software development, design, management consulting.

Recommendations

That IBM/CSC partnership

The new offerings bring IBM solutions around SoftLayer Infrastructure-as-a-Service and BlueMix to CSC customers, including integrating them with the CSC ServiceMesh Agility Platform. The agreement will bring ServiceMesh Agility Platform to the IBM Cloud Marketplace. More: CSC said the IBM alliance will help the company grab a piece of Gartner’s predicted $210 billion market for application services in 2014 and help continue to pivot the solution provider around as-a-Service solutions.

How Dell segments out the server market

As detailed by Dell’s Forrest Norrod: We typically think in big animal terms. The true hyperscale market is a very small set of customers, maybe the top seven to ten players. The scale-out customers sit below these, and include Web tech, HPC, and the large financial institutions for their quant farms. The core enterprise comes next and includes converged, high-value workloads and volume workloads, and finally there is the SMB/value segment.

Don't confuse influencers with check-signers

Tracking the exact mechanics of bottoms-up shifts in IT is as hard as tracking “real cloud” spend, if not harder: I would listen to developers, but more likely an architect or head of development than allow the grass roots to start buying and using anything they wanted. I am not naive enough to believe that developers don’t go out and look at neat new stuff, a developer happy and content to just do maintenance on existing software is a rare commodity indeed.

[S]ome outfits do still see coding as a risk to be costed, rather than a realisable benefit to be paid for.

Robert Brook

Mesosphere bringing Twitter's infrastructure secret sauce to the Global 2000 (451 Report)

As Coté Memo subscribers know I’ve been working on a report on Mesosphere. It now up, as alway available for 451 clients. Here’s the 451 Take: As with vendors like CoreOS, Docker and Red Hat (and the work around Google Kubernetes), Mesosphere is rethinking the infrastructure needed for cloud-native applications. We see a growing demand to rewrite and re-platform the bulk of applications existent in the consumer and enterprise spaces to fit into mobile and tablet form factors and take advantage cloud infrastructure.

My big ass report on developer relations and marketing

I’ve been working on a large (30 pages in lovely PDF) report on developer relations and marketing, especially, though not exclusively, targeted at people like cloud and service providers who are discovering the need to cater to developers. It’s published now. As with most of my work, I’ve tried to inject a bunch pragmatic, tactical advice alongside just enough macro “trends and drivers” nonsense to make the case for why you should care and then how you should start planning what to do next.

Cisco's 19 years of mega-growth

Since being tapped to lead Cisco in 1995, Chambers has grown the company from a $2.2 billion hardware manufacturer to a $48.6 billion network hardware, software, security and services powerhouse that’s more bullish than ever on becoming the world’s No. 1 IT company. Cisco had 3,827 employees when Chambers was appointed CEO. Today, there are more than 70,000. Also, a somewhat random DevOps callout from a senior executive:

OpenStack: It's easy if you're a full stack developer

“OpenStack talent is a rarified discipline,” McKenty said, adding, “to be good with OpenStack, you need to be a systems engineer, a great programmer but also really comfortable working with hardware. You need to understand how the infrastructure works under the covers.” … “There’s 2,000 people working on OpenStack on the vendor side, and the customers can’t compete with HP to hire OpenStack engineers. So they’re relying on us to make OpenStack work for them,” McKenty said.

Distributed transaction is, I would say, it’s an anti-pattern, and it is very hard to code in if there are like writes in transactions that need to happen in different places, in different databases, it makes it very difficult to make sure everything works really well.

Yoni Goldberg, Gilt