Coté Memo #081: The best steak I’ve ever eaten, and the slow train problem

Tech & Work World

How Microservices Fixes the Slow Train Problem

I write little columns for the internal Pivotal newsletter we have sometimes. Here’s one that’s about to go out.

The ideas of “dependencies” and “coupling” are important touch points for understanding and conveying the software delivery benefits of a microservices approach to architecture.

“Coupling” between services means that changes to one service have a big impact on another service. Coupling is considered bad in software architecture. Among other reasons, strong coupling usually means that each service can only be released as “fast” as the slowest changing service. For example, you might have an identity service and a reservation lookup service. Let’s say the reservation service can be updated weekly – the team working on it is fast! But, the identity service releases takes six months. Thus, the reservation service is forced to deliver on a six-month schedule.

Among other things, microservices remove the release cadence dependency. The goal is to allow each service to evolve as fast as makes sense for the business. Of course, there are some “new problems” to address:

  1. Ensuring backward API compatibility is a good idea. If we remove or change parts of identity services’ API and don’t change the reservation system, things break. Thus, it’s good to slowly remove functionality (or never do that!) with lots of testing, with the ability to rollback changes if/when things go haywire in production.
  2. Services should be able to isolate failures in order to “quarantine” errors in other services. If there’s an error in the identity service in production, we’d like the reservation service to gracefully fail. Operations patterns like the circuit breaker included in Spring Cloud, help manage these types of operational complexities.

Another benefit of decoupling services comes from shorter release cycles. The longer you wait to release code, the more code you’ll bundle into a release. Six months worth of code, across multiple services is a lot. When errors occur in production – and they will! – finding bugs in this ball of yarn will be much harder than finding the bad code in, say, a week’s worth of code.

Train Tracks

Think of it as train tracks. If five tracks all converge at one point, a problem on one of the tracks can cause confusion and delay for the other trains’ schedules—they’re strongly coupled. If each of the five tracks operates on its own schedule without having to converge, then of course there is no cascading schedule problem.

New Pivotal Cloud Foundry Release – a $100m/year business

Pivotal Cloud Foundry diagram

Pivotal Cloud Foundry 1.6 – there’s a new version of the product I work on (well, not coding, but you know, in my capacity of whatever it is I do). Check out my quick summary of what’s in it and, from the dormant analyst in me, an attempt to write-up the customer momentum we have.

I notice that most coverage of Pivotal doesn’t really focus on the business side of things, which is going excellent – like, we make real money and all that! Other than being nifty, I like that aspect because it means people (“customers”) find our work actually valuable enough to pay for.

If you’re interested in more “market talk,” check out the podcast I did with James Watters on the topic, GM of the business.

And, here’s some more coverage of Pivotal Cloud Foundry 1.6

Shameless Self Promotion

Quick Hits

Fun & IRL

Untitled

I that steak at Roast in Detroit. I think it might be the best steak I’ve ever had. Would eat again, many times.

Sponsors

Meta-data

Coté Memo #080: Come on, register for this God damn webinar

This week is a lull in travel. I’m closing out the year by going to lots of DevOpsDays (Charlotte, where I’m speaking, and Silicon Valley next week), a few internal summits, and my first Gartner show, where I’m speaking in a sponsored slot.

Tech & Work World

Shameless Self Promotion

Journey Time

I finished up my “cloud native journey” series recently. The real title should be something more like “how not to fuck up your cloud strategy.” Obviously, it explains the type of thinking and environment that Pivotal Cloud Foundry is built for, but I spend most of the time discussing “culture” change in an organization, regardless of what technology you use.

Check out the series, and if you’d prefer the hear me present it, we have a three part webinar series, the first one is out next week, Nov 5th with the next two coming out in December, on the 1st and then the 15th.

There’s also a preview of the first webinar in the form of my slides if you want to poke at it.

Back to Evernote

Clearly, I’m the kind of person who switches between things a lot. After a long time using the old plain text files in Dropbox approach, I went back to using Evernote. I missed the “all in one thing” nature of Evernote and the ability to put images in there. This is sort of possible with markdown and plain text files, but not as easy.

After re-wiring all Drafts to save things to Evernote and a few weeks of usage, I think it’s pretty good. The iOS apps are responsive enough, and I also like having 7 years of my stuff in there. The related notes it shows in searches are interesting. The geo-location’ing that Evernote is also interesting. I enjoy looking through my digital past with as much data as possible to refresh my memory.

Now that I’m not getting briefed all the time (and instead spend most of time creating content rather than in meetings) I don’t actually take that many notes.

Quick Hits

Fun & IRL

Untitled//embedr.flickr.com/assets/client-code.js

At first, I thought this was a costume of a motion capture suit. “Light Up Stick Man” makes a lot more sense.

Sponsors

Meta-data

Coté Memo #079: No Comment, Slack Behavior

Tech & Work World

No Comment

Big news for the company I work in this week. Sadly for my desires to write about and link to interesting stories on it, I have to take a pass. It’s bad form for employees to comment on any of this stuff; and since I worked at Dell on strategy and M&A for software and cloud, it’s double a bad idea. There’s a lot of good write-ups out there, enjoy them.

Slack Behavior

I complain about Slack a lot in the SDT podcast, but, really, it’s a good, effective collaboration tool. The more technical people use it at Pivotal: we’re waiting for the sales and corporate marketing people to get in there. Once everyone gets in, I think it’ll be great. The idea that it not only cuts down on email but speeds up decision making (and, thus, action) is very true, anecdotally for me at least. Daily I find myself about to send an email and then thinking, “I should just write to the person in Slack or put this in the channel.” In that respect, it’s much like instant messaging, to be sure.

In the marketing/evangelism groups I’ve been in, we don’t do much with the integrations – early on we played with things like Trello integration. The integrations clog the channel up a bit.

What I’d like to see more of, in our use, is thinking more about how we use: making the implicit explicit, as it were. For example, we had a discussion about what the “available”e icon means. Does it mean someone will respond back quickly? Nope, not in out Slack “culture”: it doesn’t really mean anything, people will reply when they reply.

The other thing we should try to do more is create channels for ongoing “threads” of conversation. For example, we have a #DevOpsDays channel to discuss our participation on those conferences.

Anyhow, it’s a good tool. Slack is at that difficult point now where they have to balance throwing in new features and changing nothing at all. It’ll be fun to see what they come up with. I’d love to have a Google Hangouts/Skype/Zoom that works perfectly and seamlessly. They used to call it “unified communications,” and it’d be nice to have another go at that.

Travel

I’ll be at several events this Fall and Winter:

If you’re at any, I’d love to meetup and talk with you.

Recent Podcasts

Recent Posts &co.

Quick Hits

Sponsors

Meta-data

Coté Memo #078: Spiceworld 2015, Spiceworks Momentum, Enterprise Use, and DevOps

Tech & Work World

I was at Spiceworld, briefly, last week. This is Spiceworks’ big user, annual conference in Austin; they have one in London as well. I’ve followed Spiceworks for many years (from RedMonk to 451 Research) and have always liked their IT management approach: their business model is to be the Facebook of IT by giving away the systems management software for free and then selling access to the users to advertisers, vendors, and others. They also have a data practice which has some interesting, deep pools of data.

Last week they announced several new services and features, and also made some exiting ones free. They have a hosted (cloud!) offering that I’d missed seeing; that’s one of the things they made free (down from $10/month). As ever, I think their ambition is to monitor and manage as much IT as their user base wants. They don’t always provide the deepest functionality (saving that for their “real” customers who can sell more sophisticated tools into the user base), but they balance the “you get what you pay for” product management track well as their user momentum shows:

Spiceworks momentum, as of 2015//embedr.flickr.com/assets/client-code.js

The numbers from there are not entirely consistent as they’re a mix of “users,” “monthly unique page views,” and whatever Spiceworks told me in briefings. That is, the thing counted has likely changed over time. I feel like getting a million “users” over a year is high (from 5m to 6m), but, whatever: just check out the general shape of the thing and you realize there’s something going on there.

Some other momentum figures:

  • One good, recent figure is “2,000 new members a day.”
  • Another one from Sep, 2014: Spiceworks being used by 1.8m organizations.
  • Spiceworks currently has “over 400” employees, up from 225 in Nov 2013.

One theme this year was the expansion, up-market into “enterprise.” If I recall, Spiceworks considers “enterprise” to be 500+ employees, and the rest is “SMB.” For them, that’s fair, but be warned if you think of enterprise as something more like 10,000+ employees.

Over time, the share between “small” and enterprise has been growing:

  • 2009: 13% enterprise, 87% small (from my notes)
  • 201?: 20% enterprise, 80% small (“previous to 2015”)
  • 2015: 40% enterprise, 60% small (from SpiceWorld 2015)

This year, they reported 71% penetration into F500 accounts.

The phrase “DevOps” was flashed up on the screen a few times and mentioned in meetings. In general, I see “DevOps” as only being applicable to organizations who are working on and deploying custom written software, their own software. (Sure, you could adopt the same principals for packaged software, SaaS, etc….but would you?). As it expands more, Spiceworks could concern itself with managing custom written software – somehow – which would be interesting and consistent with their general strategy of grabbing as much IT department land as possible.

Quick Hits

Meanwhile:

Sponsors

Meta-data

Coté Memo #077: Avoid going from “VP of Having a P&L” to “VP of Special Projects”

DevDaysDays Chicago

I’ll be at DevOpsDays Chicago in a few weeks, August 26th to 27th. If you want to go and haven’t registered yet, you can use the code PIVOTAL10 to get 10% off, which gets it down to like $170 or something. It’s excellent value for a tech conference, plus you can see me speak and staff a booth! While I’m up there, on Aug 26th, I’ll be speaking at the local Cloud Foundry Meetup.

Tech & Work World

Stacking the Deck

I’m working on the second part in my “cloud native journey series” (part one was an overview and brief summary). Here’s an excerpt from my draft on greenfield journeys, on selecting the right initial projects:

Selecting your first projects

If you’re a small team, or a small company, selecting the project to work on is likely easy: you probably just have one application, so select that! In larger companies, there are often 100’s, of not 1,000’s of application and projects you could pick from. You want to pick one that will have customer value (that is, be customer facing) and will give you feedback once you deploy it (people will use it a lot, it won’t just be shelf-ware). You also want to pick a small enough project that getting it into production is possible in a short amount of time, let’s say 3 months at the maximum. Finally, if things go poorly, you want it to be a somewhat low profile project so you can sweep it under the rug if things really go poorly so you can live to greenfield another day.

This last point is no doubt contentious to the purer minded of y’all out there, and I can sympathize. We should strive for truth and transparency! I’m sure you’re lucky enough to be in a corporate structure that rewards the value of failing (learning), but think about your peers who are not so lucky and work in caustic corporate culture that punishes any type of failure by “promoting” the former “VP of Having a P&L” to “VP of Special Projects.” In such cases, you’re given the chance to advance to the next place on the board by success, so you’ll want to pick a project accordingly. Of course, the point is that as you build up the success record of failing fast, as it were, you’ll be able to change said caustic corporate culture around…hopefully. While a bit dated, the 2010 booklet, The Concise Executive Guide to Agile has a detailed discussion and methodology that’s helpful for picking your initial projects.

There’s a different type of project you can choose as well, what I like to think of as a “moribund” project. It fits all the criteria above, but already exists and just needs to be shown some love. One of our customers, Humana, profiled this strategy. Their Vitality project wasn’t getting the engagement levels they wanted: just 3% of potential users. They wanted to triple engagement, getting it to 10%. As they detailed in their keynote at this year’s CF Summit, after reving that project with a more agile and cloud native approach, they were astonished by the increase in engagement to over 30% of potential users. They then parlayed this success into two other, small but important projects and are not on the path to transform how applications are done company wide, beyond the greenfield.

At ~3,500 words, I need to cut down the full piece a bit. We’ll see what comes out the other end of the chute!

Shameless Self-promotion

Some recent items from me/us:

More from “cloud native” land

I’m not sure if you’ve noticed, but the infrastructure niche of the tech world has gone crazy for “cloud native.” Consequently, I follow it a lot and type that phrase a lot. Here’s some recent items I’ve found:

Quick Hits

Fun & IRL

7 Minute Workout

I’ve been trying to the old 7 minute workout via an app (there’s a NYTimes one up too). Not having exercised for, let’s see…none of my life, it sure is hard and just the right amount of time and pain that I keep doing it.

We’ll see what happens.

Sponsors

Meta-data

Coté Memo #076: How cloud native makes customers awesome

Follow-up

  • The piece on “cloud journeys” I excerpted from last time is now posted.

Tech & Work World

Cloud Native

I’ve been writing some pieces on “cloud native” of late. It’s a term we’ve been using at work to describe what we’re all about. Here’s an excerpt from an internal newsletter piece I drafted today:

You’ve probably coming across the term “cloud native” frequently. James Watters has an excellent post on the topic, but I wanted add some background for y’all here. We’ve made “cloud native” an umbrella term to describe what Pivotal Cloud Foundry does for our customers. It’s shorthand for how we make our customers awesome: our platform gives them the tools and processes needed to start deploying their custom-written software weekly, if not daily, along with the tools needed to keep that software running happily in
production.

With this platform and knowing how to use these cloud superpowers, our customers become truly agile: frequently changing both their businesses and IT processes to keep competitive, e.g., they can think of a new business idea on Monday and have it up and running by Friday.

Speaking of this, if you’re interested in migrating to cloud-land, check out an excerpt from Josh Long’s upcoming book, Cloud Native Java. on the topic. Also, of course, you can get the developer experience for free for two months.

Upcoming Conferences

Shameless Self Promotion

  • Last week’s Software Defined Talk podcast: “Once we settle the important topic of lawn management in Texas, we discuss the circus around HP dress codes (and the actual lack of them), HP/Stackato, GitHub and the ALM market, and the odd fate of the GPL in commercial software land.”
  • Torture your friends with three ways of modeling the ROI for DevOps.

Quick Hits

Fun & IRL

No fun this issue, just work.

Sponsors

Meta-data

Coté Memo #075: Dealing with legacy code in a cloud native world

Get your lurn on – this weekend!

https://player.vimeo.com/video/121473651?color=01786e&byline=0&portrait=0

Do you want to bone up on your product management skills? Check out this two day workshop from Craftman PM. I used to work with Prabhakar and he’s anything but boring when it comes to opinions around product. Check out more details, and if you use the code COTE when registering, you’ll get $250 off!

Follow-up

W Austin

As I mentioned last time, we stayed at the W in downtown Austin last week. It was nice! The “wet” (W-speak for “pool”) was nice with in-pool bar service.

Tech & Work World

Dealing with legacy code

//platform.twitter.com/widgets.js

I’ve been working on a series of blog posts (which we’ll then slap into a PDF – hey, presto! Whitepaper!) on “the cloud journey.” Here’s an excerpt from the first part summarizing the challenges of “the legacy journey”:

These groups have a full portfolio of existing IT and applications that they must maintain and grow. There are many “obligations” owed to the past and they often operate under many more constraints than the other two types of teams. Their challenge with Pivotal Cloud Foundry is planning out how to methodically “slice off” parts of their existing applications and re-platform them as cloud native applications. These teams are metaphorically tasked with rebuilding the jet engine mid-flight.

Legacy teams are often looking for fixes to lingering, systematic problems they have (the relational database can no longer scale) and the effects of too much technical debt (“our system is so burdened and fragile that it takes weeks to do a release”). The challenge these teams have is that all of their time is taken up simply keeping their applications up and running, leaving them little time to work on new functionality in their application. Worse, when there is time to add in new functionality, the legacy system is so ponderous (and often poorly understood) that changing it takes much longer than it should.

To me, the challenges here are about balancing risk perfectly, knowing when to keep doing “the wrong thing” despite the allure of “the new thing.” Eventually, these teams have to choose either to “give up” or “go for it”: If the risks of making changes are too high, they must quarantine the applications in questions. Or, if the risks seem acceptable, the teams have to start systematically re-platforming and re-writing the backing services and applications themselves.

DevOps at Solarwinds

I was on a panel for Solarwinds online conference, thwackCamp. It was fun, actually. Check out the recording and a piece written about it.

Quick Hits

Fun & IRL

Movie Time

I say Amy) last week. I wasn’t expecting to like it much (we just wanted to see a movie, and Kim wanted to), but it was actually good. You know, tragic and such, but good.

Sponsors

Meta-data

Coté Memo #074: “Let’s start an anonymous club.”

It’s mostly links this week, with a big add video ad for my pal below:

Get your lurn on

https://player.vimeo.com/video/121473651?color=01786e&byline=0&portrait=0

Do you want to bone up on your product management skills? Check out this two day workshop from Craftman PM. I used to work with Prabhakar and he’s anything but boring when it comes to opinions around product. Check out more details, and if you use the code COTE when registering, you’ll get $250 off!

Tech & Work World

Quick Hits

Fun & IRL

Things are working out

It’s our 10th wedding anniversary (yay us!) so we’re treating ourselves to a little downtown Austin fun. We’ll be checking out the newish W down there. I’ll report back if it’s zaney. They got vinyl in the bar, man.

Leave your shoes at the door

This is my new favorite song. I listen the rest of ’em on repeat all the time now-a-days.

Sponsors

Meta-data

Coté Memo #073: If you like tater-tots, go to Minneapolis

I’m in transit between Minneapolis and San Francisco right now. The MSP airport is delightful, with a long mall at the base and concourses reaching out, it seems civilized.

Follow-up

  • I had lunch with one of you today who said, “looks like you started up the newsletter,” to which I replied, “well, if I can send one more out and then not do it the third time, then yes.” So, here’s number two. Almost to fail-o-victory!

Tech & Work World

Coté Content

Quick Hits

Fun & IRL

“Nothing in particular”++

Suggested sound-track for reading this chart.

Trends in religious affiliationn

(Via @bruces)

That looks like relaxing chaos

I like the Power Ranger show too much. I don’t like the content too much, but the relaxation of what it looks like to be the show runner. The show has a predictability and stability to it, and an audience of adoring kids. And it looks like, if you get the whole Power Rangers idea and mythos, it’s hard to screw-up.

Sponsors

Meta-data

Coté Memo #072: Since last time…

It’s been forever since a memo! Here’s this week’s. I’ve tried to craft a work-flow that will allow me to collect links I want to share, in addition to shameless self-promotion and the occasional commentary in here…and actually send these out weekly. We’ll see what happens.

Travel

DevOpsDays Amsterdam - Thursday June 25th

I’ve been traveling a lot recently and have more coming up. The main thing is going to lots of DevOpsDays. Sometimes I’m lucky enough to speak at them, but the main part I like is talking with old friends and meeting people who are trying to sort out what exactly DevOps is and if/how it applies to them.

I’ll be at DevOpsDays in Minneapolis next week, and I may be at the Pittsburg and Chicago one.

If you’ve missed them, you can see recordings of my talks from Austin and Amsterdam (you have to go 40:30 in to find mine).

Tech & Work World

All about me…

Quick Hits

Sponsors

Meta-data

Coté Memo #071: How to eat a bubble at #ApacheCon

The Cloud Foundry Summit is coming up on May 11th and 12th, in Santa Clara. It’s a great chance to dive into Cloud Foundry ecosystem both on the technology side and to hear how organizations are using Cloud Foundry to become Software Defined Businesses. Register now with the discount code COTE and get 25%, which will bring the price down from $250 to about $187.

Follow-up

  • None this week.

Tech & Work World

ApacheCon 2015

It being in Austin, I’m at ApacheCon this year. The ASF was nice enough to give me a media pass, which Pivotal being a big sponsor wasn’t necessary, but I thought it was a sweet gesture, the kind of sentimental stuff I appreciate. I used to do media training with them (come sit with a real analyst for 5 minutes) which I always enjoyed immensely.

I’m helping man the Cloud Foundry booth a bit (we have plenty of folks keeping the Pivotal booth humming since we do a lot of data stuff in this community and launched Geode today).

Today the traffic was pretty slow (the data folks had more), but the nature of people we talked with was more interesting than volume. I’ll see how it pans over the next few days, but my theory is that ApacheCon is good more for business development (partner, etc.) than for “lead-gen” (finding potential customers, working on retaining existing ones). Indeed, I talked with one of the fellas at another booth and he turned out to be their biz-dev guy, who echoed this theory back at me.

Also, they served lunch at Threadgill’s. Yuh!

Jevon's Chicken Fried Steak

(“Introducing a Canadian to chicken fried steak” photo no actually from today. Also: pie!)

A bubble-talk bubble

It’s like there’s some coordinated PR effort going on: have you noticed how much “there’s a bubble talk, yes/no?” talk has been going on of late? There’s this interview with Marc Andreessen, some horseman of the digital apocalypse vitriol, and more from Scott Kupor at Andreessen’s outfit.

The most recent Exponent podcast is the best overview of the topic, which I’d recommend, along with Ben’s write-up.

Quick Hits

Fun & IRL

How to eat

One day I hope to do a “series” called “how to eat.” It’ll go over the proper eating procedures for various types of food. When I pitch this to people, they get confused. Why would you need that? Well, for example, what’s the proper way to eat sushi? How would you explain how to eat a hamburger and onion rings to someone who’d never seen it? What do you do with all those little bowls of stuff you get a Korean restaurant? When you’re eating at one of those European hotel breakfast buffets, what’s up with all that lunch meat? How do you eat a taco properly, or a chalupa (as we call all tostada like things in Texas)? You get the idea.

Just think of how fun it’d be to make videos of all that! And then blogs-cum-books, and so on. Even a podcast.

The further part of the dream is couple it up with the series my wife would do called “You’re doing it wrong.” Each episode would be about the modern day etiquette practices that people often overlook. People would be going about putting on a wedding (“if you’re family helping out, don’t try to hijack the agenda”), a baby shower (“don’t just buy random stuff, figure out the style they want and don’t deviate”), visiting with friends (“ask if you should strip the bed when you leave”), and so forth, and Kim would bust in after the initial montage of things going wrong and say, “you’re doing it wrong!” and then go on in the rest of the episode to explain things like, for example, how you need to figure out if Christmas gift-giving is done on the “give them whatever you think they want” vs. the “give them only exactly what they asked for” methods.

The “cross-over” would occur every now and then (maybe during the credits) where I’d stumble on with some food-related thing (“here’s how to eat at a wedding”) and basically be a buffoon that my wife would roll her eyes at (“as long as the bride and groom are having a good time, don’t be afraid to fill your plate with those mini steaks! Is this an open bar situation?” [wife rolls eyes])..and then she could come on my show occasionally and tell people how they’re doing it wrong (“always bring over a nice bottle of wine, no matter what the host said!”).

Sponsors

Meta-data

Coté Memo #070: Lost in the review hole, Lord of Computing

There’s few links today, just some pointers to now published material that I’ve alluded to recently, and some moaning on needing to be a better team-player.

Follow-up

  • We got up to 100 subscribers, so good job there, y’all ;)

  • As several people wrote, the word I was looking for in that discussion of lower case letters is “semiotics”, the study of symbols.

  • The podcast I excerpted from on the operational needs of cloud platforms (and people who don’t capitalize words) is now up. There’s audio, of course, and a full transcript.

Tech & Work World

I am not scalable

I’ve been struggling with extending my reach of effectiveness at work. That is, working well with others. When it comes to “getting things done,” I’m very good at it if I do all of it on my own, and every knob and wing-ding from concept to delivery is under my control. Once someone else gets involved in more than a faceless way, things slow down. I almost give up because I can’t stand to wait.

This is very much so driven by the blogger culture that I “grew up in” over the lat 90s and 2000s. You would just type, hit publish, think of new edits, hit publish again, etc. It gets enforced by a (non-pairing) programmer mentality where you can do all you need on your own (short of last code review, perhaps), pretty much.

In the white-collar world, things are rarely like this. First, there’s often at least one other person who has to approve your work. This is often to the benefit of the message and making sure the company does well. Second, there are often “gate keepers” who control the release of product into the world.

Each of these steps (and others) are intended to add value to the end product, but I still struggle to value those steps myself and, thus, find the value in them. Obviously, that’s an annoying problem for all people involved. Now, watch me click publish…

New Podcast

I (re-)started a new podcast today, here’s the first episode:

How to demo your cloud poop, don’t smoke corn silk, and other advice for people who lived in the 1930s – Lords of Computing Podcast 001

After catching up several times over the past few months, John Willis and I decided to reboot our podcast from long ago. In this first episode, we talk about putting together good demos for cloud platforms, among other things.

We’ve re-named it the Lords of Computing, borrowing an ancient domain name I’ve had forever. Take a listen, and subscribe! (This will be three podcasts I do regularly now, which is great: it’s one of the things I like doing most.)

Fun & IRL

No fun today, just work. I did notice that there was a half pot of coffee left at 3pm today. Something was going wrong.

Sponsors

Meta-data

Coté Memo #069: Chili Cheese Tots, shift key avoidance syndrome

Follow-up, Follow-forward

  • The column I excerpted from last time is up, over at FierceDevOps: Software-defined businesses need software-defined IT departments. Tell me what you think; they asked me to write a monthly piece, so I’d love to get some ideas for topics going: got any?

  • I got some good feedback on the podcast sponsorship meanderings. Apparently, there’s pretty good money in tech podcasts. The next thing I’m curious about is if the advertising actually works…or how people even measure it.

  • We have 98 subscribers right now – exciting! Tell one of your pals to sign up so we can get above 100 for the next one.

  • I’ll be at ApacheCon (in Austin) next week. We’re hosting a related event during the conference if you’re interested; I advised them on pizza ordering (either Home Slice or Conan’s – we’ll see what happens). It’d be fun to chat if you’re there. A few weeks on, I’ll be at DevOpsDays Austin, giving a talk and hanging out. The Cloud Foundry Summit is coming up and, as you might guess, I’ll be there as well.

Tech & Work World

no caps

Today, I bring you an excerpt from an upcoming Pivotal Conversation episode with Andrew, due to be published this week:

Coté: You know, I was thinking. There’s something I wanted to ask you. You have, like myself, pretty broad experience in the IT world over a couple of decades now, which is odd to think about. I think you’ve had your head in a slightly different silo than I have, in the early days. I think you can answer something that’s been bugging me. What is up with people who don’t use the shift key? Like they never capitalize anything. They have good punctuation. They don’t capitalize the beginning of sentences. Am I over thinking this? Is there … I feel like a lot of technological people that I know, I shouldn’t say a lot, there’s a fair amount of them who don’t capitalize things. Because they’re sort of like programmers or operators, I know that they pay close attention to syntax. I feel like it must be a conscious choice. Right? They must have decided, sort of like: one day I decided I’m not going to put 2 spaces after a period. Done. I never do that. Right? So, I ask you again, what’s going on with people who don’t capitalize things?

Andrew C Shafer: I think it’s just a hipster…I sometimes do that. It actually is conscious.

Michael Coté: See. This is … I’m not passing any judgment. I have no judgment to pass at all. I’m genuinely curious. When that affectation is applied intentionally, what the semantic thing is going on there. Is it, what’s that fancy word, like the study of symbols? Symbiotic? There’s some sort of symbiotic thing going on there.

Andrew C Shafer: Quite frankly, I don’t know how philosophical you want to get, in an encore performance here, but I don’t actually see the point of capitalization. Seems redundant.

Michael Coté: Now, that’s a statement right there. I like it. That’s something meaty. I think, this has been my theory.

Andrew C Shafer: With punctuation and spacing, what purpose does capitalization…

Michael Coté: Yeah. Yeah. It can all be inferred, basically. Right? You know. This would also highlight why, if this was like 2002 and we were complaining about the kids with their T9 texting, that would be a whole other discussion of no capitalization. In this case, I think it’s this subset of people who are technologically inclined. I feel like the answer you just gave is probably what’s going on with a lot of them. It’s like, I want to have an economy in my writing that strips out anything that’s unnecessary.

Andrew C Shafer: Yeah. It’s a protest against hierarchy.

Michael Coté: Namely the hierarchy of typefaces that are taller than others.

Andrew C Shafer: Exactly. We don’t need a class system.

Michael Coté: We need a class system. That’s an entirely different type of “class system” we’re talking about. Not separating things out in their value. More logos space class system.

We then talk some sort of tech stuff. I’ll drop in a link to the episode once it’s published. Or, just subscribe to the podcast feed to get it once it’s published.

“the feeling of being informed when you get to the very end”

Ben Thompson pointed out this good, short interview with The Economist’s Tom Standage

I love their Espresso app, and here’s some stats on it:

It’s $3 per month. It’s doing well: We’ve had about 600,000 downloads. Weekly reach is about 200,000 readers, daily reach is about 120,000 readers. 175,000 weekly subscribers have enabled free access to Espresso. So in all of those ways, it’s good.

…I don’t know all those term well enough, but let’s take a stab. I’ll assume “daily reach” means people paying for it regularly. So, the revenue could be something like:

$3 X 200,000 = $600,000

I’m unsure if that 175,000 weekly readers is on-top of the 200,000. I’m a weekly (digital) subscriber (through airline miles!) and I added it (meaning, I don’t pay “extra”). Anyhow, like many people I probably don’t actually read the weekly edition of The Economist cover to cover, but I do tend to read the daily Espresso.

Someone in tech needs to do that model. It’s a great format: a few hundred words per story with a summary of 3-4 stories at the end, and then the usual Economist numbers fest. If you could draw lines around “enterprise IT” (that is, not Apple, Google, Facebook, and all that), I think you’d have something pretty good. You’d need to define the companies, technologies, and topics you cover there, and then just take the Espresso approach. Their “model” is world news and business, of course: much larger. Scoping down to just some chunk of the IT world would be easy enough for 1, maybe 2 people to boot-strap in. And fun!

Quick Hits

Nice chart on Uber growth:

//platform.twitter.com/widgets.js

As you’ll recall, I threw together this one from rumored revenue in the Wall Street Journal:

Uber's rumored net revenue

I like to use these charts to illustrate how fast a software defined business can grow and that, you know, it’s a thing.

Fun & IRL

Eating Right

We visited with friends for Easter this weekend.

On the way, I enjoyed a rare road-food treat at Sonic:

Sonic Chili Cheese Tater Tots

To make up for that, our friends made excellent food each night, for example:

Eating right

I didn’t get a picture of the lamb-chops. Or the omelet stuffed with left over smoked pork.

#WorkingFromHome, lanyard signaling

A reader wrote in:

One tip on working from home from a friend that works at Cisco. He wears his Cisco badge on a lanyard when he works at home, so even when he goes to get a drink from the fridge the family knows he’s still “at work”. He just holds the badge up when his wife asks him to flip the laundry or take out the trash. For me, I’m still trying to get French doors put on my home office door to help w/the noise. Looking forward to your tips.

Man, I think my wife would kill me if I did that, but it does get to the point. Sometimes signaling is all that’s needed. My wife is very good at responding to a door closed signal. Whether it’s locked or not she assumes that means no interruptions and will keep the kids out, even I actually don’t mind. So, I have to be very mindful of door closed or not.

Sponsors

Meta-data

Coté Memo #068: Are they really making $48,000 a month just talking about Apple?

Tech & Work World

Podcasting Rates

Brandon shared some podcast revenue estimates with me from the Hot Pod newsletter recently. I’m all for there being lots of money in podcasting, but they seem bonkers high:

Then there’s Standard Broadcast Co., independently produced shows that hang a banner under the same ad sales network. This includes three of the most popular tech podcasts: John Gruber’s The Talk Show; Marco Arment, Casey Liss, and John Siracusa’s Accidental Tech Podcast; and CGP Grey and Brady Haran’s Hello Internet. Those three programs have in the 80,000 weekly download range, and command a rack rate of $4,000 per ad slot ($50 CPM) with up to three ads per show, often sold out well in advance.

So, doing the math on this:

  • ATP will have 2-3 ads per episode. Let’s go bonkers and do 3.
  • ATP has 4 episodes a months, excluding holidays and such.
  • So: each episode would be (3 ads X $4,000) = $12,000
  • (4 episodes a month) X $12,000 = $48,000

Really? $48,000 a month?! Let’s half that: really? $22,000 a month?! Let’s 1/4 it! Really? $12,000 a month?!

I could go out and check rate sheets for various podcasts (see some at Standard), but I’m curious if these numbers seem high to y’all. Cracking the nut of pricing for “infrastructure” and “enterprise” podcasts has always been hard.

Back at RedMonk, we could paid about $2,000-$4,000 per “sponsored episode” (think of “native advertising” for podcasts before such a concept existed – we did a lot of interviews with early Puppet users, for example). I was once offered somewhere between $1,000 to $2,000 per episode for a podcast that I was wanting to start at 451 (thanks, you know who you are!); it got killed by 451 because they saw ads in podcasts as too close to commissioned work…or whatever.

Now that I’m in marketing, how would I think about paying for podcast ads? Well, we target Global 2,000 customers at Pivotal, so our deal size is large (we had 40+ customers in 2014 that accounted for almost $40m in bookings – you can do the math there for average deal size, and crimp it around a bit for a realistic distribution). This means that if I got just one “really good lead” from a podcast…I’d pay almost anything. If I’m looking to help create a $300,000 to $5m deal over the course of 1-3 years…what’s $3,000 here, $10,000 there? (This also throws some cold water on people who get freaked out about webinar, analyst, and other enterprise sales marketing price-tags: it’s because the end-goal is huge).

Still, it’s hard to know what good rates are. I’d love to hear what y’all think and what’s worked or not. You know, it’d be nice to get some revenue for my co-hosts and I for Software Defined Talk – and it’d also be good for any podcast deals we end up doing at Pivotal.

On another note: if the rates from Hot Pod are even half (or a 1/4th!) realistic, the independent analyst business model is looking even better if you can monetize a podcast.

For reference, here are weekly downloads of my podcasts (which are mostly Software Defined Talk at the moment):

Podcast stats, , as of 2 April 2015

You can check out individual episodes numbers as well. (And, check out the fancy chart styling in the preview version of Microsoft Excel for Mac!)

Quick Hits

Fun & IRL

No fun today, just work.

Sponsors

Meta-data

Coté Memo #000: No jokes here.

Tech & Work World

“What kind of company do you think we are?”

Here’s some excerpts from a FierceDevOps column I submitted yesterday.

Quick tip: if you’re in a room full managers and executives from non-technology companies and one of them asks, “what kind of company do you think we are?”…no matter what type of company they are, the answer is always “a technology company.” That’s the trope us in the technology industry have successfully deployed into the market in recent years. And, indeed, rather than this tip being backhanded mocking, it’s praise. These companies are taking advantage of the opportunity to use software and connected devices in novel ways to establish competitive advantage in their businesses. They’re angling to win customer cash by having better software and technology than their competitors.

And, later revisiting my old IT – SaaS = what? trope…

There’s another “horseman” in the broader industry that’s driving the need to change how IT departments are structured: the rise of SaaS. Before the advent of SaaS across application categories, software had to be run and managed in-house (or handed off to outsources to run): each company needed its own team of people to manage each instance of the application.

451 Research ChangeWave Cloud Usage

Source: 451 Research/ChangeWave

As SaaS use grows more and more, that staffing need changes. How many IT staff members are needed to keep Google Apps or Microsoft’s Office 365 up and running? How many IT staff do you need to manage the storage for Salesforce or Successfactors? Indeed, I would argue that companies use more and more SaaS instead of on-premises packaged software, the staffing needs change dramatically: they lessen. You can look at this in a cost-cutting way, as in “let’s reduce the budget!” Hopefully you can look at it in a growth way instead: we’ve freed up the budget to focus on something more valuable to the business. In most cases, that thing will writing custom software. That is: developers.

Quick Hits

tumblr April Fools

Fun & IRL

#WorkingFromHome

I’ve been collecting some little aphorisms and such on working from home when you have young kids. I find it extremely challenging, and rewarding at the same time. I’m curious how other people cope. Part of the issue is that, with a 1.5 and 5 year old, about once every 30 minutes someone is crying or wants attention. There’s just no letting up. If you’re the parent working, you have to just ignore it, which is weird.

Here’s something I wrote up recently:

The end of the day is the worst. Your family asks you every five minutes when you’ll be done; they start wanting to play with you. At the same time, you’re desperately trying to find time to get done. Each time they interact with you, it slows you down.

The answer, of course, is the same as always: you have to control access to you in a way that;s not assholey. Lock a door, go to a distant room. You have to hide.

Five year olds aren;t up to speed on the cost of context switching and haven’t read the maker/manager essay.

Anyhow, I think there’s a good presentation in collecting enough tips and, more helpful, counseling to make it work.

Sponsors

Meta-data

Coté Memo #066: The best time to post is an hour after closin’ time

From yesterday, posting here a bit late.

Follow-up

  • It’s been awhile, a little over a month. I hope to see y’all more regularly. I was reading the excellent TechReckoning Dispatch and thought: what the fuck am I doing over here?

Tech & Work World

Meanwhile, at work…

I’ve been up to hijinks over at Pivotal. Check out my recent posts there:

  • We did a round of briefing analysts on a bundle of announcements around Pivotal Cloud Foundry. It was fun being on that side of the table again.

  • The podcast with @littleidea is fun.

  • In addition to the blog work, there are several guest columns lined up. I’ll of course link to them once they’re hear. Perhaps I can get some chunks of drafts in here to gauge interest, per usual.

Talks

I’ve been pitching some DevOps related talks here and there for the rest of the year. DevOpsDays Austin is coming up, and I’m hoping I’ll get the chance to talk there. Pivotal is sponsoring it, so you can come talk with my co-worker Abby (@ab415) about Pivotal Cloud Foundry. Or, hey, just get some free shit. Why not?

Also, I’m trying to get together some panels going over developer relations. As you may recall, I wrote an introductory level report/how-to on the topic while at 451. The plan was to drive consulting work off that, of course, but now it’s just sort of orphaned. It’d be fun to keep that theme of research going, if only by having some discussions in public about it time to time.

Quick Hits

Fun & IRL

Sponsors

Meta-data

Coté Memo #065: Back home, finally

After two weeks away from home, I’m finally back.

Sponsors

  • This Memo is sponsored by The Craftsman PM – Amp up your skills and get to the top at this Whole Product Workshop Feb 21-22 in Austin and Mar 7-8 NYC. Grab a spot at 10% off for just Cote Memo readers (use code: cotememo62) before it’s all gone: http://bit.ly/cotememo62

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Follow-up

Some reader follow-up on the Mexican matches from @MordodeMaru:

That match-box sure is another mindfuck. I think the key is the de lujo rather than the Clásicos. De lujo means high-class, luxurious and those objects (except for the Parthenon temple) are considered high society objects. It’s a very typical Spanish expression to say something is de lujo to mean cool, and this is something publicity picks up very frequently.

Tech & Work World

The industry analyst business – meta-level

I finally wrapped a long post on the tech industry analyst market. As I talked about in a recording for thenewstack.io analyst podcast, I originally wrote the first draft back in April of last year when Ben Thompson first launched Exponent.fm. In a more recent episode, he went over how his business has been going (very well!) which reminded me that I should finish up the post.

In the proceding time there was new data out there which allowed me to rate his success by revenue, broadly. And, since I’d left the analyst world, I felt a little more free in analyizing that world.

Anyhow, it’s been nice to hear the reception from other analyst types. In talking through the piece with Alex Williams today, I think the part that I found lacking (as I disclaimed in an aisde at the top of the post) was an explanation of how this new crop of analysts could better attract buy-side customers.

What the new analysts do is mostly “vendor sports” which is appealing to the investment community (who wants to know how to allocate their money), vendors (who want ideas and competative intel), and the smaller “general audience” that just wants tech news. Buyers want advice about what IT to buy and how to use it. Alex and others are exploring ways of doing that…but there could be a lot more done there to marry-up the kind of work Ben Thompson, Horace Dediu, and even RedMonk does with Wirecutter style reviews (credit to SDT co-host Brandon Whichard for the Wirecutting framing which I think is spot on).

The issue, as I do cover in the post, is that doing these kinds of reviews and advice for enterprise technology is really expensive. Imagine what it would take to build out labs and tests to evaluate all the OpenStack distros, running in various modes…and then compare them to VMware and Microsoft virtualization. Or to evaluate all the ERP software out there.

I think it’s technically possible and would even be interesting. The problem is the opportnity cost for people involved: if you had the analytical and technical acumen to do that kind of testing, you can probably make more money working for an actual enterprise or vendor.

The problem always comes down to what people want to pay for, and it doesn’t seem easy to make money off the hard work in IT analyst land. That’s part of why Gartner has such a strong position, and, as I advise in the piece, an area they could defence against well.

As a side-note, I left out something I’d noticed about Forrester while putting together charts for the piece: they seem to be loosing profits, I’m not sure why, could be for growth or something bad.

Quick Hits

Fun & IRL

It looks like you’re supposed to drink 3-5 cups of coffee a day now. That and two glasses of wine a day, and we’ll finally be livin’ the life!

Honestly, I can’t keep up with all this stuff. Is there some source for nutritional advice that can be trusted more than 24 months?

Meta-data

Coté Memo #064: I’m calling from Mexico, someone has stolen the Venus de Milo!

Follow-up

  • We’re up to 90 subscribers and one of you went a helped out one of our sponsors (The Craftsman PM), so thanks!

Tech & Work World

Sayulita

Week in Mexico

I had a nice chance to spend the week in Mexico this week. A friend of mine rented a house here in Sayulita and asked if we wanted to go along. Since I work remotely, so long as there’s a fast enough Internet connection, I’m good to go. Now, the family is frolicing around on the beach while I type away in cyberspace. What a world!

That advice from The Hitchhiker’s Guide was right, though: we should of brought more towels.

Allow to comment on the odd design of these matches:

Week in Mexico

First off all, the Venus statue. Sure. Makes sense for matches. And there’s a train, of course, and the Pantheon goes along with the statue…plus you can win $1,500 pesos? I’m not really sure what’s happening here.

I like to think there’s a caper where someone stole the Venus de Milo and is transporting it on a train. Perhaps an overworked Mexican detective is working with interpol investigating where this Mexican train is traveling and trying to find the statue. I don’t know, they sent the Venus di Milo to a musem in Mexico, or it was being transporting between the Panama Canal and Boston, or something. A sort of The City and The City situataion? Hijinks occur, and they end up solving the mystery with some match sticks.

That’s probably it.

Here’s some photos of the area:

Week in Mexico

Week in Mexico

Quick Hits

Fun & IRL

Sponsors

  • This Memo is sponsored by The Craftsman PM – Amp up your skills and get to the top at this Whole Product Workshop Feb 21-22 in Austin and Mar 7-8 NYC. Grab a spot at 10% off for just Cote Memo readers (use code: cotememo62) before it’s all gone: http://bit.ly/cotememo62

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

Coté Memo #063: Working at Pivotal and Yak shaving

Follow-up

In reponse to the analyst access commentary from last time, a reader wrote in:

Are you familiar with Securosis? They’re a security-only analyst firm.

Their business model is pretty different – everything they publish is free, and make money through sponsorship and inquiries etc. They have a model they call totally transparent research. I don’t know how much they make – but apparently they make enough to cover themselves.

Tech & Work World

Working at Pivotal

Cote Pivotal Linedrawing

I started a new job earlier this month at Pivotal. I haven’t had time to write an informal overview yet, but instead I did this interview/post on the official Pivotal blog.

There’s also a follow-up piece that I haven’t promoted too much yet. I’ve been busy. Hopefully I’ll have my feet better under me.

So far it’s been great, I’m really liking it. We have so much cool stuff at Pivotal and are getting crazy traction, with around $40m in Pivotal Cloud Foundry bookings last year.

Quick Hits

Fun & IRL

Sponsors

  • This Memo is sponsored by The Craftsman PM – Amp up your skills and get to the top at this Whole Product Workshop Feb 21-22 in Austin and Mar 7-8 NYC. Grab a spot at 10% off for just Cote Memo readers (use code: cotememo62) before it’s all gone: http://bit.ly/cotememo62

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

Coté Memo #062: The Problem with Analyst Access

We’ve got a new sponsor this week, see below. There’s a 10% coupon. I’m planning on going to the event to get my lurn on.

Also, I wrote this pretty fast. Pardon messups.

Tech & Work World

The Problem with Analyst Access

One of the core opportunity/problem diachotomies in the analyst industry is “access”: access to the analyst’s insights, access to the analysist content, and access to the analysts themselves. Gate-keeping this access is the basis for much of the business: paywalls, paying for consulting, etc.

However, that business model can be a dangerous leaky abstraction in seamingly trival ways. For example, I recently wanted to sign up for RSS feeds for all the published research from Gartner, Forrester, IDC (actually, they have several, but no “everything” feed I’ve found yet), etc. (I already know 451’s feed URL, which is admitly not super easy to find, but there for finding). They don’t really seem to have them. There’s not full text in these feeds, of course: you need access to their paywall to read the full text. But, it’s important for me to know what they’re publishing and I imagine other folks would like to know.

Here’s how most access to analyst content seems to happen, you ask the AR person to send you a copy. You rarely get your own account (it’s too expensive, most analyst customers seem to think). Instead, there’s one account that an analyst relations people uses, and you can ask them to look up things for, like a reference librarian. And yet, analyst shops rarely put out a “card catalog” (that RSS feed) that lets us without accounts know what’s published. Thus, I don’t know what I should be requesting.

Of course, the analyst side of this is “well, you should stop being a cheap-ass and pay for an account, doofus, problem solved.” And, having been an analyst for almost 8 years of my career, I can’t fault them for wanting to get paid. I’ve got 5 kids to feed too!

But this need to control access so tightly that I don’t even know what they’re publishing is sort of a non-starter.

Once again, this brings me back to “access” as the number one variable and lever you can play with in the analyst business. GigaOm toyed with this when they set a very low price in their early days (around $70-200 a year for an individual subscription, depending on discounts) and I look at people like Ben Thompson as hacking that even more (he’s just $100/year). My alumus RedMonk took another tact years ago and just ditched the paywall, getting paid for consulting and other things (like their growing[?] events business); someone once derisivly called RedMonk a “patron” model, which is sort of right, but only a tiny bit.

So, in other words: hey analyst shops, can you get some RSS feeds? (Hopefully, they exist, and I just haven’t found them yet. Remember: all published research, not just blogs and announcements.)

Cloud SOTU, 5 years late

I had the privilege of talking to the Austin cloud user group earlier this week. I’d given the opening talk back in 2010, so they asked me to come give an update. The themes and many of the charts will be familer, but I’ve been honing down to a more specific message: you should get a platform…and probably not build it on your own.

Quick Hits

Fun & IRL

Too much fun this week to document. Stay safe out there.

Sponsors

  • This Memo is sponsored by The Craftsman PM – Amp up your skills and get to the top at this Whole Product Workshop Feb 21-22 in Austin and Mar 7-8 NYC. Grab a spot at 10% off for just Cote Memo readers (use code: cotememo62) before it’s all gone: http://bit.ly/cotememo62

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

Coté Memo #061: On the tedious need to have an opinion

Tech & Work World

Having an opinion, or not

In the types of jobs I’ve found myself in over recent years – analyst, strategist, “content producer” in the form of podcasts and blogs – you have to generate a lot of opinions. The best actually seem to really care about the things they have opinions over and can express, at length, why they think like they do. Think about the ATP crew or any of the other podcasts out there: they really care about Apple! Ben Thompson is another font of opinion, and his content is very interesting for it.

I seem to have powered down my opinion engine of late: I just haven’t cared as much. I find myself taking a “wait and see position” more than not: in the technology space, I’m more interested in learning how people are using technologies and about how the actual technologies work than having a strong opinion about which their metaphysical essence.

I find that “having an opinion” also guides a lot of managing teams. A manager should have an opinion about how the team runs, what their work product looks like, how they’re rated, and ways to improve. That takes a lot of opinion, expressing it, and enforcing it. At an individual level – managing yourself – the same applies.

This leads me think that we need opinions to simply tell us what to do day to day and how we should rate how we’re doing. It feels something of a wrong conclusion: you’re not supposed to be overly subjective in “managing.” And yet, it seems to me that most interesting – not always the most profitable – “work” is driven by a strong opinion, and following it to its logical conclusion.

Quick Hits

Fun & IRL

My old cache of D&D books. And there's a whole 'nuther box!

Whenever I dig around in the attic, I came across the two (!) boxes of Dungeons and Dragons books I have up there. It makes me long to DM again. After coming across this “Three Sad Wizards” module and listening to the first episode of Total Party Kill, I wrote up the beginning of an adventure that night sitting up in bed.

Here’s the summary I tapped out at the top:

“The player wakes up in a dungeon with no memories of who they are and must quest through the valley of five rivers [can you tell I’ve been reading Game of Thrones?] to discover their past. The player should either be a warrior or a thief, they can decide which at some point early on.”

Sponsors

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

Coté Memo #060: Mark all cookies as read

Follow-up

Tech & Work World

Whatever happened to “mark as read”?

Like most old cyberspace people, I lament the death of Google Reader and RSS daily. I still use Feedly (coupled with Newsify it’s alright – I wish Flipboard would work with Feedly but, you know, it doesn’t, because monetization or some crap, I guess), so I have that going for me.

Now that are so many other options out there for “reading interesting links,” I find that what I like about RSS readers is that they mark a story as read. Things like Flipboard, reading tumblr, HN, and all that seem to lack that feature – I don’t want to see the same thing twice, or, more likely, five times.

Which brings us to the “fun links in your social networks app du jour”, Nuzzel. It’s nice enough, but like all the other apps like it, it has no mark as read feature. I keep seeing the same stuff over and over. (And if you recall how I actually use Twitter, ignoring my “real” timeline in favor or a list I made, apps that depend on the Twitter timeline are borked for me).

As I alluded to above, Flipboard was the best when it worked with Google Reader – I could load up all the social crap it works with, and Google Reader, and it was tidy, marking as read my RSS stuff and letting me swipe through all the other nonsense that would sate my FOMO goblins.

So, a plea to all you FOMO app people: add mark as read to your app. Even better: add Feedly integration, they must have APIs or something, right? Make it an in-app purchase! I bid 20 quatloos on the new comer!

(The reason I really like Newsify – the one feature I can’t live without, as it were – is that it marks as read as you scroll, like the old Google Reader! The Feedly app sort of does that, but it doesn’t have real scroll, instead it flips through pages, making me have to shift my eyes from the bottom of the screen to the top each time I “scroll.” I know, this seems like a tiny thing, but when you read as many feeds as I do, it’s now.)

Quick Hits

Like most folks, I was gone for two weeks. These may be a bit stale.

https://twitter.com/nntaleb/status/550370028437385216

Fun & IRL

Sponsors

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

Coté Memo #059: Containers make butter-scotch pudding delicious and floors shine

Tech & Work World

Floor wax, dessert topping

As I mention below, I’ve had more time to write reports recently. I just submitted one titled “Docker: floor-wax or dessert topping? Reflections on DockerCon EU”. It’s one of our “spotlight” pieces, which means it’s an open-ended think-piece rather than a write-up of a briefing.

Here’s some excerpts:

451 Take: The container technology Docker and the ecosystem around it is figuring out its identity while at the same time contending with a sudden rise in popularity. While early attention on Docker paired it up against the likes of VMware at, let’s say, the IaaS level, as we look at it more, Docker looks like more of a PaaS innovator. VMware would certainly like that option, and Docker, Inc. spent much of its recent conference in Amsterdam talking more about Docker-as-PaaS – through the lens of “microservices” – than Docker-as-IaaS. From this vantage point, it looks more and more like dotCloud never really stopped being a PaaS vendor, and instead, with under its new name of Docker is just evolving the nature of PaaS.

The technology promises at least two things: (1.) an alternative way of virtualizing workloads on servers using the underlying containerization technology and (2.) a DevOps friendly way of packaging applications for deployment on cloud and cloud-like infrastructures. Much of the vendor sports watchers fixate onto the first use-case, looking to thrust Docker into a Thunderdome with VMware. However, as both Dockers – the open source project and the startup – have evolved, it’s becoming clear that the second is perhaps the more interesting promise, long-term.

Over the next 12 to 18 months, expect to see much shuffling and toe-stomping on the ecosystem dance floor. Indeed, with so many interests, large and small involved, it wouldn’t be surprising if the landscape changed dramatically over the next year. Early moves like the Rocket container standard effort point towards conflicting (or at least “differing”) interests, and with deep larders and large revenue sources to protect behind many, large Docker ecosystem member’s backs, anything could happen with something as miraculous as a floor wax that also makes butter-scotch pudding taste so terrific.

One of the ongoing theories I hit on in the piece is that (a.) cloud is all about developers, but, (b.) the PaaS market is small compared to others, so, (c.) what up with that? As you can imagine, I posit that the interest in Docker-cum-containers could change the market-dynamics a bit. We’ll see.

I’ll throw a link in here and all the usual places once it gets published, I’m guessing next week. I put in three or four charts too, so look forward to them if you like charts.

(Lucky[?] for you, this is the only place you’ll see the silly dessert topping floor-wax reference as the copy desk asked me to take that out since another analyst used it recently.)

How I use Twitter: ignore the timeline

I’ll let you in on a secret: I don’t really pay attention to my main timeline in Twitter. There’s too much crap in there that I’ve ended up following (1,910 account, to be exact) since I started using Twitter in 2006.

Sometime ago, I created a list called “Focus” that I actually follow. It has just 127 accounts in it and it works well. There’s some tricks of how to do this depending on which client you use. I can stand the official Twitter web and iOS (actually, I haven’t looked at it in awhile) apps so I use TweetDeck on my desktop and TweetBot on my phone. In both instances, you can choose to focus on a list.

In TweetDeck, it’s easy: you just move the column over that you want. You’ll notice in the below that my “timeline” is nowhere to be seen:

Switching around columns in TweetDeck

In TweetBot, it’s a bit more hidden, you have to “long tap” (is that what you call it?) on the title bar until it pops up a list of lists, then select the one you want. You can see what it looks like after I long-tapped on the title bar:

Viewing a list instead of your timeline in TweetBot

Sometimes I go slightly insane and think there’s not enough from Twitter. Recently, I thought I’d take a look at the timeline and see what was in it, what was going on. It’s a fun walk down memory lane as I discover clusters of accounts I’ve added over the year. I found a bunch from when I thought I didn’t get enough local and “real-world” news so I have/had several Austin accounts and things like Meet the Press. There’s also folks from long ago in there that I vaguely remember. And, going in and out of the analyst world, there’s also a lot of people who are or were clients at RedMonk and 451 Research. Lots of IBM. Lots.

I’ve been pruning that main timeline this week in the hopes of perhaps actually using it. I’m not sure it’s worth it, but it a good distraction-as-entertainment.

Quick Hits

Fun & IRL

No fun today, just work.

Sponsors

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

Coté Memo #058: Cloud ads, amateur coffee drinkers, orchiwhu?

Follow-up

Why the apparent reversal in the thinking about coffee? Earlier studies didn’t always take into account that known high-risk behaviors, such as smoking and physical inactivity, tended to be more common among heavy coffee drinkers at that time.

Studies have shown that coffee may have health benefits, including protecting against Parkinson’s disease, type 2 diabetes and liver disease, including liver cancer. It also appears to improve cognitive function and decrease the risk of depression. {{{More like: so long as you keep drinking coffee, you will not get depressed. A subtle, but important difference.}}}

However, the research appears to bear out some risks. High consumption of unfiltered coffee (boiled or espresso) has been associated with mild elevations in cholesterol levels {{{Doing good so far…}}}. And some studies {{{Uh-oh…}}} found that two or more cups of coffee a day can increase the risk of heart disease in people with a specific — and fairly common — genetic mutation that slows the breakdown of caffeine in the body. So, how quickly you metabolize coffee may affect your health risk.

Let’s get something straight: if you drink less than two (real talk: let’s say 4) cups of coffee a day, you’re just a recreational coffee drinker. I, sirs, am a professional.

Now, I need to go run my DNA in the hay-doop cluster to see about that “genetic mutation.”

Tech & Work World

Cloud Ads

In case you didn’t know, IT is my hobby and my job. I like to collect pictures of cloud ads in airports and otherwise (see above about keeping the flow of coffee steady).

Here’s some from my recent trip to Amsterdam:

2014-12-04 09.46.41

2014-12-02 23.10.13

Send me some #cloudads!

One of my favorite IT ads ever, from 2008:

New Compuware Ad

I like the look on the dude’s face in background: “not gonna happen, ladies.”

Quick Hits

//platform.twitter.com/widgets.js

Fun & IRL

  • No today fun, just work.

Sponsors

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

Coté Memo #057: Is Cloud Foundry a Thing?, EU Coffee, and developers

Tech & Work World

The Cloud is Developers

It’s an exaggeration, but for the most part “cloud” is all about supporting developers. What I mean by this is that it’s not exactly the best way to run packaged applications: there’s VMware, Linux, etc. for that it seems.

When I was working on cloud strategy at Dell, I’d often joke that we should do some field material (“field” == “sales”) that was a crude decision tree, like you’d see in magazines. The point of it would be, only sell cloud to them if they get to the “sell cloud” node in the tree. I doodled out that diagram, so here it is for your entertainment:

Cloud buying decision tree

We have some recent survey data at 451 that lines up nicely with this theory:

TIP-Thurs-Cloud-110614-pic

To put it another way, if you know a way to use cloud that does not involve developers, you’re probably educated enough not to need a cheesy decision tree…but if you’re not sure, start with the crude tree.

Is Cloud Foundry a thing?

We had an internal thread in Cloud Foundry, the foundation announcement of course being the cause. The main question from those who don’t follow PaaS, middleware, and appdev was, basically, “is this a thing?” Here’s what I typed:

I think it’s important, indeed. PaaS has never really taken off (beyond Salesforce, Heroku, and EngineYard), esp. in private PaaS. Part of the issue is that there has been no “standard” to agree on. Historically, unless you’re Microsoft, middleware needs a standard (formal or de facto) to adhere to (think of J2EE, the LAMP stack, even rails, etc.) for wide, enterprise adoption. Cloud Foundry appears to be “the OpenStack of PaaS.” With IBM on board, HP, Pivotal/VMware/EMC, and others there’s some good backing: even better, those companies seem to have commercial offers that they take very seriously.

Aside from “the big folks,” I also think relatively tiny ActiveState/Stackato is a good proof point. They’ve been in GA with Cloud Foundry for a long time and seem far from dead. My hope is that Cloud Foundry (along with Docker-as-PaaS)finally ushers in a new middleware era. We’ll see.

Slow Business Travel

Last week I was on a week long travel tour taking me from Santa Clara, to being stranded in DFW, to Amsterdam. It was fun, but a week is a long time. Each work-day I rush to finish things up at the end, to cram as much in as possible. Time seems to move quickly.

When you’re doing business travel, time moves slowly. You realize how slow time can move if you’re not distracting yourself with the check-inputs/do work/check-inputs loop constantly. My brain is wired to always check on Twitter, email, listen to music, file expenses, go get a glass of water: find anything to do but the core work.

Plane time reminds you that things can move slower. Of course, what did I do with most of my plane time? Well, after working on what work projects I could, doing some planning…I watched movies and read books.

Quick Hits

Fun & IRL

European Black Coffee

I’ve been lucky to be in Europe twice for work in the past month or so – the OpenStack Summit in Paris and DockerCon in Amsterdam. I drink black coffee, a lot of coffee. Probably too much given the history of heart attacks in my family.

Having drank European black coffee a lot, I can tell you that it’s not like American black coffee. It’s pretty, well, “motor oil” class. Thick, bitter, and far from smooth. Perhaps this means American coffee is “watery coffee,” which, having just grimaced down a cup of EU black coffee, sounds lovely.

The type of coffee you want, then, is an Americano. I’d always thought it was an odd drink, but in fact it’s the best simulation of “normal” to me black coffee you can get in Europe. I just had two cups, and found myself thinking: finally, some good coffee!

Sponsors

  • Is it too late for cloud? – if you get this soon, come check me out in what will likely be the last webinar I do this year. You can always catch the reply too.

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

We have 76 subscribers now – thanks to everyone for joining in!

Coté Memo #056: the $110,000 a year blogger, investing in barf bags

Tech & Work World

Quick Hits

2015 Preview preview: invest in barf bags

Here’s the concluding text from out 2015 preview for Development, DevOps, and Middleware channel (one of the practice areas I oversee at 451) which I submitted to the copy desk today. We’ll see if it gets through:

Every which way you look, you hear “cloud”: a call to rip and replace the previous infrastructure layers and replace them with this ineffable new things of magic. For those with more gray hairs in our beards than not, this sounds like a gut-wrenching return of the climb up the roller-coaster ride of IT: time to put in place new layers of IT replacing old layers that never delivered on the promise of “business/IT alignment.” Well, it’s time to take some Dramamine (or at least get a barf-bag) and ride the roller-coaster. New cloud technologies and practices are proving to be better suited for delivering on business/IT alignment through the critical path of “agility.” While examples like Uber and mobile application loyalty card app like Starbuck’s are cliché by now, they point to a very real vision at the application development layer: the ability to harness developers to program the business with custom written programs. Thanks to new technologies (mostly, “cloud”) previously moribund and very un-agile industries have the chance to use IT for more than just running packaged applications, checking email, and scheduling meetings – a method of IT existence often known as “keeping the lights on.”

Over the coming years, the trends we’ve identified here will repeat themselves often: honing the software development and delivery practices (DevOps), new standards for packaging and deploying custom written applications (Docker), and the evolution of enterprise architecture practices and tools. The last body of work – enterprise architecture – must start evolving at pace with “the kids” of DevOps who have little knowledge, appreciation, or use of the staid body of work known as “EA.” The bathwater has become so murky that the baby can be hard to find, but we as industry must do so: extracting the best from EA and throwing the accumulated muck out the window. Mainstream companies, ever risk averse, are eager to find a steady-hand when it comes to applying DevOps to their software delivery pipelines. The DevOps community has done some work there, but it tends to espouse a raised earth theory of process change over an evolutionary change program. Enterprise architects themselves will need to understand how their roles changes in the rapid application delivery life-cycles of cloud and DevOps and help those communities evolve and become more “enterprise-y.” Otherwise, it’s out that window with all the brown water.

The Independent Analyst

As you can imagine, I’m fascinated by the independent analysts out there.

Those individuals who setup shop, hang out a single, etc. What I always want to know is how much money they make.

My analyst hero, Horace Dediu seems to have joined a foundation removing him from the mix. Ben Thompson (aka @stratechery) is one of the more recent ones to join this mix.

He has paywall (“subscription”) that costs $100 a year (or $10/month) and gets you daily updates, email access to him, a member’s forum, and other stuff.

In a recent podcast he mentioned he now has about 1,100 subscribers (in a post he said 1,000).

So, at $100 a year (the discounted rate), that’s $110,000/year, plus some consulting of around $10-20k total (so far), I’d guess? So, let’s say $120,000/year. That’s in just six months!

Let’s say it takes a year to double that to a round $200,000…and even after expenses (which should be low if he never hires anyone or travels much) and taxes, you’ve got a really high paying job there. (First of all: good for him!)

Consulting can add up quickly here as his fame (and trust in him) rises. I’d wager that in year two and three the consulting would ratchet up and he could charge between $5,000 and $10,000 for a one day, low prep consulting or speaking engagement – $20,000 for a higher prep one (requiring several days of work ahead of time). Beyond that it’s a project spanning weeks, but more in the $30,000 to $40,000 range per project. At some point, an individual has to turn away consulting work because it will very dramatically and very quickly damage your daily output (have you seen how little I’ve been publishing of late?).

Ben has such a broad area of topics that I’ve always wondered who his customer is: perhaps the generic “I want to keep up with startups and high-growth IT” readers? The TechCrunch crowd (a crowd that is likely starved for “industry analysts” who are good, let alone as helpful as Ben)? His customer, I guess, is the whole “software is eating the world” crowd, which is a good demographic to target: they likely have a spare $100/year and really want the information.

Another interesting tangent here is that Ben’s success is an example of his “there’s more than just scale” counter-idea to businesses like Google, Facebook, and Uber. He’s been doing a good job explaining it in the past two episodes of his podcast, #25 and #26. This “long tail” think has always been a hope of Internet people. Hopefully it’ll work this time.

The main issue is getting the actual individuals to take the leap, go through those “dark times,” and either fail or succeed. The technology and structures are there, it just needs more meat-sacks to take on the risk and see if it pans out.

(I’ll have to finally subscribe and see what’s going on beyond the paywall.)

Fun & IRL

Lamb chops tonight.

They had lamb-chops at CostCo this weekend. Here, you can see $21’s worth in action. I just ate the last of the left-overs for lunch.

Sponsors

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

We’re up to 70 subscribers now – thanks, readers!

Coté Memo #055: It’s cold in Toronto

Follow-up

Tech & Work World

Quick Hits

“Script” for Docker orchestration

Oftentimes, I write a “script” for presentations. I never read it for the presentation (maybe I should!), but it helps me organize my thoughts and presentation. Here’s the one I used for the Docker orchestration webinar I did with CloudSoft last week:

Macro-context: the demand for building your own PaaS – DevOps, cloud, etc.

[chart on DevOps delivery pipeline, old dto solutions DevOps pipeline]

I like to reduce things down to brutal simplicity. I have a lot going on in my work and personal life so I have to leave nuance for entertainment. To me, cloud is mostly about supporting custom written software, whether that’s for something like a SaaS (from social to ERP), consumer facing business applications (like online banking), or applications used by companies to help run their business. And what that means is creating a delivery pipeline that encompass all the phases of an applications life and automates each step as much as possible to reduce bottlenecks and increase throughput. You have to look at this pipeline as a mission critical process in your business: from development to production, it’s you’re factory, the thing that helps you make money…not just a cost center. You’re pushing out incrementally improving software that runs your business.

Custom written software is the most valuable work-load for cloud, I’d theorize, where value is rated by how technology can help a company get competitive differentiation.

So, something like Docker is especially interesting because it promises to speed up that pipeline. I don’t think anyone know exactly what it will shape up to be, but it looks like the “private PaaS” answer we’ve all be looking for.

[chart with SaaS, PaaS, ISaaS, IaaS market-sizing – put OpenStack market-sizing in there next to it]

Now, PaaS is an odd category of public cloud. It seems like the perfect realization of the efficiencies of cloud, and yet it keeps limping along as a market as this 451 market-sizing shows.

Much of that revenue comes from Salesforce which has its own Force.com platform (a “PaaS for SaaS” as we call it) and Heroku.

[chart on demand for private cloud]

For some reason, developers and companies have a lust for build your own cloud: they either get their own gear or rent raw IaaS and build up their own stacks to support as automated as a DevOps delivery pipeline as possible. Maybe it’s cost (I haven’t ever heard a developer say public PaaSes like Heroku are cheap), maybe it’s the need to exactly customize functionality, maybe it’s good old paranoia and FUD (which could be justified, who knows).

Whatever the case, people want control over their stacks, and that’s where things get interesting. The more control you have, the more you have to worry about the more hassle there is.

We seem to have a long way to go to replicate the magical, effortless push to deploy demo we remember from early public PaaS days. Much of what’s needed is what’s currently going under the title of “orchestration” which, roughly, means “making sure my complex distributed system is installed and configured properly…and then allowing me to modify its runtime characteristics and upgrade it.” You know, getting the application up and running, tuning its performance ongoing as needed, and upgrading it.

[insert chart showing rise of new automation tools/brands]

This area has long been the domain of custom shell scripts, manual configuration, and, thankfully, in recent years configuration management companies like Chef and Puppet (who are taking over the automation reigns from OpsWare and Bladelogic).

Docker has burst on to the scene of late as an interesting salve for cloud infrastructure woes. To me, it starts with the right goals: make using cloud easier for developers. That may seem subtle, but it’s different than most infrastructure software goals which is make like easier for sysadmins and auditors.

To keep pushing on the dream of being able to build your own PaaS, the ad hoc community around all of this has been obsessing about orchestration of Docker-based clouds, let’s call them, of late. So let’s look at that.

Emerging market for orchestration

Mindmap from Krishnan Subramanian

When it comes Docker orchestration, there are almost too many projects to count, and even a few products. I love this mindmap from Krishnan that shows just full this market is – and tedious for analyst to keep up with. This is a good sign, however: there’s so much interest and passion in figuring out Docker and how to orchestrate it that surely, something will work.

Emerging requirements for orchestration

When I look across what all of these projects are trying to do – and slap in some old IT Service Management think – I come up a list of requirements for orchestration. Some of them may seem obvious, but it’s always good to be explicit. If you spot ones that are wrong, or missing, you should pass them along and perhaps we can winnow down a list. We don’t need a manifesto or any nonsense like that, but in studying this space, you do find a distinct lack of architectural-level specifications and requirements – which is fine, people are busy coding.

Cluster/fleet management

  • Operate in terms of multiple nodes, not single nodes – configuring a single Docker node is mind-blowingly easy, doing it over 50 or 100 nodes gets to be tedious, esp. if you want to continually be turning over builds. Pets vs. cattle and all that.

Configuration management & Automation

  • Application modeling that describes the layout and configuration of various components – this is an old ITSM notion, “service modeling,” which got bogged down in drag and drop fantasy (just like UML). You need to model what all the different components are and how they fit together
  • Basic CRUD – creating nodes, updating nodes, restarting them as needed. You want more than just modeling what a node looks like, you want you orchestrator to actually do something.

  • Separating configuration from basic state – easily modify configuration without having to change too much about each node/image, like changing port numbers easily without rebuilding the entire node

  • Ensure proper configuration passing across nodes – passing server names and ports to servers, handing out credentials, wiring in service directories, etc.

Heterogeneous platform support

  • Support for different infrastructure, bare-metal, to plain old virtualization, to multipule clouds – some might call this “hybrid cloud” or “multi-cloud” – useful just for moving along the pipeline

Baby and bathwatering ITSM

  • Asset database to track all your cows – another ITSM trick. this starts getting into “enterprise” needs, but it handy even if aren’t tweedy. You need to know what you have out in the wild and quickly locate it when things go wrong.

  • Capacity management and adjustment of resources – not only monitoring if you’re over (or under!) capacity, but actually going back to your CRUD operations to make adjustments on your nodes. This is also where keeping configuration separate from node state is handy: you could increase memory, keeping the same configuration, for example, without having to rebuild or swap out nodes.

ABC

  • Ease of use, and esp. low cost – otherwise, why not just use a full on PaaS? This is always easy to forget, but it’s sort of the point of all of this. Ask yourself, is this easy and quick to use? If it’s not, something is wrong.

This last point is key. You need to remember that once you’ve done all the above, that’s when the difficult work begins. You still need to come up with an idea for an actual application and its features that will help your business. You need to stop orchestrating and start coding, not to mention working on the product management that will tell you what to code in the first place. Don’t get all caught up in all this Heathkit stuff: save your cycles for the most valuable thing: ABC.

[Always be coding chart]

And with that, I want to pass it over to CloudSoft to tell you how they’re helping you get closing to coding.

Fun & IRL

No fun today, just work.

Sponsors

  • FRONTSIDE.IO – HIRE THEM! Do you need some developer talent? When you have a web project that needs the “A Team,” call The Frontside. They’ve spent years honing their tools and techniques that give their clients cutting-edge web applications without losing a night’s sleep. Learn more at http://frontside.io/cote

Meta-data

Coté Memo #054: CA World wrap, Docker orchestration

Tech & Work World

Quick Hits

### AWS

There were innumerable announcements from Amazon at re:Invent this week, perhaps even more tomorrow.

Docker Orchestration

I gave a webinar today on Docker Orchestration (you can see the recording and the slides). I’ve spent time following this and looking into and tried to distill down the reasons you’d do it and the “requirements” for such a tool…it’s pretty non-technical.

In doing this research, you find that no one has really say down and specified what orchestration means, which is what I was hoping to prod someone in doing. There’s no ThoughtWorks microservices essay that sums it up, and their should be!

Thanks to CloudSoft for putting it on!

CA World sets a 12-18 month spring-trap

As I discussed in the Software Defined Talk podcast recording today (subscribe to the feed to get the show once I publish it), I’ll be looking for momemtum from CA in a year or so. Their vision, portfolio, and “slides” were all good and spoke to DevOps well at their conference this. They even had some excellent customer talks, like ING going over how they’d used DevOps. I spoke with another customer who was eager to do very genuine DevOps as well – we see this in our DevOps market studies as well.

At this point, the only thing to do is wait and see if it works out by: (1.) tracking customer adoption and, thus, revenue, and, (2.) seeing how CA fills out the rest of the DevOps portfolio, if at all.

Hopefully I’ll be able to check back in at the next CA World.

Fun & IRL

  • No fun today, just work.

Sponsors

Meta-data

Coté Memo #053: there’s a lot of earth for software to eat, day 1 of #CAWorld

Follow-up

  • It’s been awhile. The family and I were on vacation for a bit in Paris, and then I was at the OpenStack Summit.

Tech & Work World

Quick Hits

Las Vegas Conference: CA World

The longer you stay away from a conference in las Vegas, the weirder it is to be here for one. Or, maybe, it’s just that it’s always weird. I’m here for CA World now, which is an odd, interesting conference: attendance and sponsorship seems sparse but they have some good DevOps messaging.

I was last at CA World in 2010, where the message was a resounding “cloud or die!” There’s a similar message around “the application economy,” which is pretty well aligned to what I’m always going on about: developers are important, you business people should be hiring them to write applications. Coming from CA, a company never really known for having much to do with developers, this is a odd message, but it’s the one you’re stuck with in an IT – SaaS = what? world.

CA has good messaging and solutionaring around DevOps. They have release management (from Nolio), mock testing (“service virtualization” they call it), and monitoring of course, APM notably. They have lots of parts, and can put them all on a slide well. They’re also very clear about their approach being solution oriented: not DevOps products, but just ways of combining their tools together.

After a discussion with a fellow attendee, the question in my mind is: what’s the unique thing about CA that’d make you go to them for all of this? Their answer would likely be breadth of tools and integrations. The usual for a large company.

For as much effort as they put into DevOps – by my count, the most out of their class of companies – they don’t come up in the DevOps world much. One theory is that DevOps has, thus far, been product and commercialization resistant. Another might be that the message simply hasn’t gotten out. Another could be that the “DevOps market” is so small that nothing would register.

There’s a lot riding on mainstream “enterprises” committing to the idea of writing more and more custom software: that whole “software is eating the world” but. It feels true to us techies, but there’s a question of the rate of change and if it’s net-new growth. I’m also unsure how a company structures itself to take advantage of more enterprises needing to develop software.

As a round-about example, I’ve been looking into Docker and cloud orchestration software. There’s so many projects built around those problems: there’s even too many! In a software eats the world world, there’s almost too many options, making it hard for a company to cement in competitive advantage (the reason customers come to them and pay a premium over competitors – the reason companies make profits).

It’s just day one of two I’ll be here. Perhaps all the answers are tomorrow.

Fun & IRL

  • With kids on vacation, you watch a lot of TV. That Regular Show is pretty good.

Sponsors

Meta-data

Coté Memo #052: Two types of clouds and headless doctors

Follow-up

  • Hey there! It’s been awhile. I warned you, things are monkey-balls over here.

Tech & Work World

Quick Hits

Software Defined Talk #15, with guest Andrew Shafer

If I don’t say so myself, I think Software Defined Talk has hit its stride. The three of us have a good mix and tone, and I hope you’re enjoying it.

At the spur of the moment, we had Andrew Shafer on our most recent episode, so we talked at length about Docker, both at a technical and strategy level. He’d just published a good article on the topic. It was a great conversation.

Also, you can hear me complaining about how my diamond shoes are pitching my toes, which is to say, wanting someone to fix calendaring.

There’s two kinds of clouds in the world…

I’m fond of pointing out the theory that, for the most part, cloud only matters if you’re talking about developers. You’re probably not going to run packaged software – SharePoint, Lawson, SAP, etc. – on cloud stuff: the incremental benefit vs. plain old virtualization (VMware) likely isn’t there (yet?). Thus, there’s this unhelpful discuss of cloud that doesn’t distinguish between running “old (mostly packaged) software” and (mostly net-new) custom written software. To put it another way, if you were doing lead qualification for cloud deals (public IaaS/PaaS or private), the first question should probably be “how many developers do you have on staff?”

There are exceptions, etc; hence: “theory.”

An old friend of mine, Zane, and I were discussing this in email recently. In reply to him complaining about over-hyping cloud, I replied:

Yeah, this assessment is pretty much right. I think the thing about cloud, to your point, is that unless you’re going to dramatically change the way you write applications, it’s just slightly better virtualization.

Now virtualization, that’s certainly a big deal…but the step order improvement from cloud is not that big [I’d theorize].

The part people often miss about cloud is the self-service/fulfillment changes. It’s about dramatically reducing the reliance of service desks and manual IT and instead automating provisioning new IT and the ongoing management of it (server is in bad state, reboot it). [Or, as covered in a recent DevOps Cafe podcast with Tom Limoncelli: in a cloud world, tickets are filed when things go wrong, not for any old request.]

“Private cloud” is another weird thing that I’ve yet to fully understand. It seems like just setting yourself up for the same old management problems, that maybe move a bit faster, but is it really so much better than just a bunch of VMware with self-service…or moving more of your stuff straight to SaaS? [I was called the “private cloud analyst who doesn’t believe in private cloud” in a briefing recently, which seems pretty much right.]

For developers – like yourself – cloud will always be more tedious than it seems…because you guys are doing more than just installing software and using SaaSes. I think the big hope for cloud is that (a.) IT admins have to spend less time manually caring and feeding for compute, storage, and networking (much of that work is manual now-a-days!), and (b.) companies move more and more of their on-premises packaged software to SaaS. Managing GMail (or even Office 365, I should hope) should be magnitudes of order more easy than managing on-premises Exchange. To me, this migration of on-premises packaged software to SaaS is the real boon…and why SaaS tends to be larger as a market and more valued.

We’ll see how it shakes out, but to my mind if there’s a SaaS version for a product it almost makes no sense to run the on-premises packages software on your own, or even colo’d somewhere…unless you have developers on staff, in which case there’s a whole other conversation to be had.

Fun & IRL

Inside Jokes: “Good luck with no fuckin’ head”

Another one of my inside jokes is an exchange from Barton Fink, which was brought to my attention (as with so many good movie lines that have become core inside jokes) by Chip:

Mastrionotti: Started in Kansas City. Couple of housewives.
Deutsch: Couple days ago we see the same M.O. out in Los Feliz.
Mastrionotti: Doctor. Ear, nose and throat man.
Deutsch: All of which he’s now missin’.
Mastrionotti: Well, some of his throat was there.
Deutsch: Physician, heal thyself.
Mastrionotti: Good luck with no fuckin’ head.
Deutsch: Anyway.

So, next time you see an absurd situation in front of you and someone’s asking you to fix it, just sigh and utter out, “good luck with no fuckin’ head.” I’ll know what you’re saying, and we’ll high-five.

Sponsors

Meta-data

Coté Memo #051: Meetings suck, links galore

Tech & Work World

Quick Hits

Fun & IRL

Sponsors

Meta-data

I decided to shorten the template a bit, moving the boiler plate stuff to the end.

Coté Memo #050: not much on Friday, pretty boring for #50

Meta-data

Hello again, welcome to #050. Today we have 54 subscribers, so we’re +1. Keep your best behavior up for this new person! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Follow-up &co.

  • I’ll be at BMC’s conference in Orlando next week. Let’s meet up if you’re there!

Tech & Work World

Quick Hits

The Power Rangers need more sheep, also, big companies divorcing themselves

After a week off, we’re back with Software Defined Talk. This week’s episode is fun! Take a listen, and be sure to just subscribe to the feed.

Fun & IRL

I have to things from Big Trouble in Little China for you:

  1. GIFs!
  2. “You were not put on this earth to ‘get it’!”

Coté Memo #049: how to brief analysts, tech co.’s splitting up, noise canceling-enough

Meta-data

Hello again, welcome to #049. Today we have 53 subscribers, so we’re +/0. See what happens when I stop posting? I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Follow-up

Tech & Work World

Quick Hits

Having gotten three days behind, there’s a lot!

HP divorcing itself, splitting up

Divorce rate set to go up in tech-world

RoW

Dealing with analysts

Stephen O’Grady wrote-up some tips for briefing analysts. It’s a good item to type up every few years; self-serving, but helps us analysts out. As you may recall, I have gave a presentation on the topic back in January, focusing on startups.

I added an extended comment to his post, which I’ll plunk here as it highlights some of my top pet peeves in briefings:

I think point #2 (“Unless you’re solving a unique problem, don’t spend your time covering the problem”) is where people waste the most time. And polite analysts like myself let them do it. In general, discussing “macro” issues is not interesting. We know computers are awesome, businesses want to focus on using IT to make more money, and everything that came before the offering being briefed on is crap.

There’s two common patterns I see, at startups and large companies here:

  • Startups like to re-use their VC pitch deck (or something else weird), which is usually that TED-level 500 slides that takes forever to get to a meaty point.

  • Large companies often talk about “solutions” and industry needs, and all sorts of high-level nonsense (did you know companies could be using computers to make more money? I know! crazy right?! Check out this picture of a guy in a suit smiling.)

In both cases, what I want to see if the actual product, what it does (feature set), and how it does it. Screenshots and demos are nice.

When looking at a new product – be it from a large company or a startups – the default assumption I have is that the product is crap and does not work as well as promised. Like the rest of the IT world! What I want to see is the reason(s) why this product is better and solves problems in a better way.

And, as you note, sometimes there is a genuinely new thing that demands a lot of “macro” talk. Like, remember when you and I had that first briefing with 3Tera long ago? It wrapped up all of the problems here: one, they needed to educate us about what “private cloud” was (this was back in 2006 or so before that concept existed) but at the same time, they needed to tell us the actual technology stack that was supporting it (I remember you badgered them for about 30 minutes before they stopped saying “new paradigm” and started saying “Linux”).

As a more contemporary reference, I’ve had similar experiences (though better) with Mesosphere and CoreOS. The initial Mesosphere briefing I got was very “macro”: grandiose, revolutionizing how all applications would run (“So, I can run SharePoint and Lawson on this?” “Well, not exactly…all applications except those,” etc.) but once I started asking questions about the stack, it perfectly turned into nerd talk and was great. CoreOS skipped the macro talk with a simple “updating Linux sucks” and moved onto the stack (all etcd, systemd, hot/cold images, containers, etc.) and discussed how that was all different than “the current paradigm.”

And, on point 9 (“Asking for feedback ‘after [or during!] the call’”), another phrasing would be: “so, can you give me some free stuff?” I don’t think most people understand that casually and formally giving people advice is a large part of how us analysts get paid (and 80-90% of how RedMonk gets paid – 451 has a paywall, as do others). Again, I’m very polite and never really say anything, but unless I’m “friends” with the person briefing me or they’re regular, good clients…and they ask for “input and feedback” I find it rude. It’s like asking a doctor or a nurse to just “check out” some ache I have in my back instead of scheduling an appointment: I’m asking them for free stuff.

So, there you go. You could also just tell us analysts to fuck off and stop being such pansies, but hey, there’s some insight into on our our core APIs: briefings.

Fun & IRL

  • I helped host a dinner at HCTS with SolidFire. It was fun! They gave me a pair of Bose QC15’s as a thank you gift. They’re nice! There’s a built in mic. I’ve been using them and while they don’t actually cancel all outside sound, I feel like they cancel enough to make the world (and airplane) much more pleasant. They also keep your ears toasty.

Coté Memo #046: I don’t like dick-bags either, & more on marketing platforms

Meta-data

Hello again, welcome to #046. Today we have 53 subscribers, so we’re +1. The crazy pills are working! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Follow-up

  • See below.

Tech & Work World

More on marketing platforms.

One of you wrote in and asked for more detail on the platform marketing missive. As I replied back, that text was taken from an ongoing conversation I’ve been having with someone so much context was lacking. Here’s another take at the point I was trying to make.

The point I was trying to make was: your platform can probably do 50 things. Market just 1-5 of them. 50 things is too much and you come off being scary or, worse, arrogant. Developers don’t like switching to uber platforms – <gratuitous inside joke targeted at Robert Brook>Marco still uses PHP!</gratuitous inside joke targeted at Robert Brook> SOA/WS-* failed to be sustainable at winning the thought-leadership war because it was too big, did too many things. Developers just said, “uh, I just need a 3 page web application..WTF…?”

To use another metaphor, getting developers to adopt a new platform is like boiling a frog. You can’t let them know you’re doing it until it’s too late, otherwise they hop out. Again, this is where the open source process and culture is key. Unlike commercial products , OSS platforms are rarely planned out in advance. They evolve, often in an ugly fashion. And if they are “planned,” they’re allowed to “pivot.”

Remember Apache Avalon (I could never understand what the fuck was happening there)? Probably not, but I bet you remember Struts (ugly collection of code that coalesced into a platform through much patina’ing) – .do forever! You probably also recall Tomcat (based on a standard which the market had already long ago accepted – Tomcat’s pitch was “it’s free! [and works]”).

All of those were platforms, but each evolved differently. Each were destroyed/replaced by the next iteration of platforms that mostly grew up organically in the same ship-mutate-pivot-ship-mutate-pivote-etc. cycle.

You can’t plan ahead for a platform, you just have to adapt your bucket of parts to how “the market” actually uses it (here, “the market” == “developers,” sometimes “architects,” God help us). Or, have your platform be so damn simple that it does, pretty much just one thing, and then you market the shit out of that. E.g.: rails, early Heroku.

Yet another phrasing: “tech marketers: pick one thing your platform does, just one. What’s that? No! No exceptions: sit down and shut-up. Did you pick one thing yet? Good, now go market that for 30-60 days and see if it works. If it doesn’t, go through the cycle again and again with different features.”

Quick Hits

https://twitter.com/pmonks/status/517519157748039681

  • A burger diagrams go, this is a good one:

Fun & IRL

Coté Memo #047: Selling a “platform” is one of the more difficult tech marketing tasks you’ll ever do

Meta-data

Hello again, welcome to #047. Today we have 52 subscribers, so we’re +/-0. I should write more awesome stuff to get more sign-ups!

I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Follow-up

Tech & Work World

Quick Hits

  • Scores HipsterOps bingo!

  • These Pivotal people are up to something. They have a lot of pieces. Need some crazy visions. Cream on top.

Rants galore

There’s few people who speak their mind more openly and helpfully than @shanley. At least there’s someone throwing bombs.

I’ve enjoyed her weekly (daily?) rants on the OpenStack community of late.

Selling a “platform” is one of the more difficult tech marketing tasks you’ll ever do

I was discussing platform marketing recently in email. Here’s an except.

I think the market challenge [in selling a platform or “all inclusive middleware”] is forcing yourself to take on the perceptive of a blind man describing an elephant. You want so badly to be the man with two eyes describing everything; you want to go all Plato. That doesn’t work well early on, it’s too much for “the market” to consume, and they move on to simpler pitches.

Something like Apcera gets attention because it has fame behind it and they categorize themselves as a “PaaS,” a well know category (on the other hand, “PaaS” is a very confusing term once you look at more closely!). They enter into the conversation with these two things and then can helpfully deflect to being “policy driven” (a “fabric”), which a difficult concept to understand.

Sidebar: do you remember when Microsoft and VMware were going on and on about “fabrics” about 3-4 years ago? There was even vFabric! I never really understood what they meant (from their slides, not having dug into it) and I suspect the market didn’t either.

You use a good word below [in the email I’m responding to]: “orchestration.” And taking on that servicing the blind man and his elephant mentality, that might be a good way to describe these new types of platforms and middleware: we orchestrate the execution of enterprise applications. The thing to do is to pretty much stop there and just go out with that message. Describe what the problem is, what “orchestration” means, and then slowly trickle in your actual technology and how you’re different.

What’s frustrating to me is the conversation around things like Mesosphere and CoreOS. Both seem cool, but there’s very little talk about the business use of those technologies. Are we just talking about running “stateless” web and mobile apps (read: NOT enterprise software), or something else?

To go even more abstract, one of the problems I see in the developer world at the moment is that there’s very little “business analyst” think: that role that used to sit between the customer and the developers that understood the processes and needs of business and could tell the developers what that meant for code.

I don’t expect developers to map out business processes, but I think most platforms out there do. Developers need help understanding those processes. And once developers understand that their job (largely) is to write the code (or build the system) to automate and “computerize” those business processes, I think platforms slot in well. Instead, the developer world is so focused on consumer tech that the idea of a complex decision tree of events, workflows, etc. always seems foggy and foreign.

Thus, I think many “enterprise” platforms get a frustrating reception in the wilds of the web. If you remember the old Crossing the Chasm advice, the first thing you need to 5-10 good reference customers who can explain to their peers what the problem is and how it gets solved. Early on, selling the technology for the technology sake is difficult. This is also why so many “platforms” seemingly start as open source: they build up momentum and “reference customers” by giving themselves away for free for awhile.

Fun & IRL

Coté Memo #046: Who’s got the story?

Meta-data

Hello again, welcome to #046. Today we have 52 subscribers, so we’re +/-0. I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Follow-up

Quick Hits

Hipster level final boss, EMC, Beef Jerky, and more OpenStack vs. Docker

This/last week’s Software Defined Talk is up. It’s a fun one!

Fun & IRL

Coté Memo #045: Double up to catch up. You have to spend money to make money. When you see this cup empty, just refill it w/o asking. QED

Meta-data

Hello again, welcome to #045. When we hit #050, let’s all have an extra drink – I know I will! Today we have 52 subscribers, so we’re +1. Good job, subscribers! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Follow-up

  • Sorry to have missed yesterday. Things be busy around here. It should even out next week, but then travel will start. I just got requests for two more trips today, for some fun consulting around DevOps, so that’ll be nice.

Quick Hits

Tech & Work World

This Week’s Software Defined Talk episode is awesome, I just need to publish it.

As they used to say: <eom>

Fun & IRL

https://twitter.com/BenKuchera/status/515234822135230465

Dune reference always wins.

Coté Memo #044: Very little today. Work, work, work!

Meta-data

Hello again, welcome to #044. Today we have 51 subscribers, so we’re +/-0. I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Tech & Work World

Quick Hits

Fun & IRL

https://twitter.com/cwood/status/514841459594256385

Coté Memo #043: EMC + (HP XOR Dell) == what? “Fabrics” returning, and the joys of bicycle jousting

Meta-data

Hello again, welcome to #043. Today we have 51 subscribers, so we’re +/-0. I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Tech & Work World

Quick Hits

  • Mirantis wants to part ways with Red Hat and it’s easy to see why – Mirantis has several “strategic” relationships and investments (vendors that invested in them, partner with them, etc.). As they expand, you know, it can get weird.
  • Why Rackspace will fly solo: the market is evolving – nice 451 commentary from Scott Ottaway and Carl Brooks: “The selection of an internal candidate for CEO also indicates that Rackspace will focus on its strategic direction of targeting customers that value managed services tightly wrapped into public and private cloud services. It will also focus on offering cloud services across multiple platforms beyond OpenStack, including VMware and Microsoft, and emerging services like bare-metal servers and devops.”
  • Dell World speaker schedule without star keynote; panel to open show – one doesn’t want to read too much into DellWorld line-ups at all. But, hey, less big stars, which I think is fine. I usually skip the big interviews because they have nothing to do with the company, whatsoever.
    More converged cloud theory – “They prefer buying a whole lot of stuff from one vendor, and we were open to the acquisition because it is in the interests of the customers that we are serving. We had a lot of customers asking us to do managed clouds, others were asking us for hardware recommendations. These were signals to us that it would not be a bad idea to have an end-to-end solution ready.”
  • Summary of Cloud & Data Center Automation Content at Engage – I’ll be at BMC’s conference this year. Oddly enough, the first time ever. Why odd? I worked there as a programmer for 5 years, covered them for about 6 years at RedMonk (OK, I went to an analyst conference they had which was very nice). It’ll be fun! If you’ll be there, let’s get together. I know the Swan and Dolphin and the boardwalk area like the back of my hand (thanks, IBM!).
  • Mesos Founding Father/Twitter Fail Whale Slayer Hindman Joins Mesosphere – eventually, these dudes or CoreOS will be a big deal. Perhaps both of them, but probably not unless they merge which wouldn’t really make sense, I don’t think.
  • Mobile security pain overwhelms the enterprise – damn mobile phones. The thing you have to remember is that each computer is kind of different: different enough to require new management stacks. You can’t use mainframe tools to manage Unix, can’t use Unix tools to manage x86/Windows/Web, etc. New devices mean new management tools, including security. Stay safe out there!
  • Article: Q&A on Kanban in Action – I should check this out. I have a theory that if I can apply Kanban to my white-collar work, things will go better. I can never really figure out Trello for “make that presentation” or “write that report.” Worse, my co-workers and folks on my team could give a crap about Kanban. The Office toolchain is just fine for them, thank you very much…which is fine.
  • The need for internal digital evangelism – I make this point all the time: if you want to change how things are done, you need to show-up, a lot. Sorry.
  • “Fabrics” are probably coming back – “We are seeing more and more customers looking at multitenancy requirements, and the word of the day is microsegmentation – how do you segment the infrastructure from end to end so you can run your risk analytics next to your Hadoop infrastructure?” Remember when everything was a “fabric.” We had “vFabric,” Microsoft talked in terms of fabrics, etc. I always thought it was a hella-cheesy, but I get the sense we might see the metaphor com eup again.
  • Linux? Bah! Red Hat has its eye on the CLOUD – and it wants to own it – nice letter from the Red Hat corporate strategy party.
  • Does Alibaba offer a ‘golden opportunity’ for U.S. small businesses? – I think what you (people who care about infrastructure-y stuff in the enterprise world) want to pay attention to here is how the hyper-scale Chinese web companies are positioned to be just like Amazon, down to AWS. As I understand it, AWS isn’t massive in RoR (“rest of world,” outside of Gringo-land on both sides of the pond), so there’s gap to fill. Everyone likes cloud, but lots of folks don’t like Yankees.
  • Heroku Rolls Out Metrics to Help Users Optimize Performance – they’re doing their own systems management. Fun!
  • BMC Software Sues ServiceNow for Patent Infringement – hey, it’s the thing Big 4 vendors do. “You kids (who used to be on our lawn and who, really, we bought the lawn from…hrm)…get off my lawn!”
  • Chinese Tourists Find a Movable Feast Best Left Behind – a large European city filled with dog poop and rude people! Sacrebleu! (See you in Paris for the OpenStack Summit!)
  • Puppet Labs hands strings to admins with updated DevOps tools – PuppetConf just wrapped and there’s some new features.

Rumors of EMC merging with HP XOR Dell

As I mentioned in Twitter, I think this would be a bonkers idea. Cats and dogs. Those companies all dislike each other. They’re so big it’s difficult to know how they’d properly integrate together. It looks like the rumors have blown over.

However, having worked in M&A for a few years, you can’t dismiss things like this too much. You have to remember how long acquisition projects are too: they rarely just pop-up over the weekend and have been churning around for 6, 12, even more months. At this scale, it’s also important to look at divestitures or “carve outs,” companies selling just part of themselves.

The bigger question would be: why? What advantage would a merger between EMC + (HP XOR Dell) get you? You could fire a bunch of shared staff (HR, finance, etc.), consolidate some campuses. Maybe get some benefits from account sharing. On the account sharing front, Dell’s “mid-market focus” would be a better match, on-paper, with EMC’s “enterprise focus.” Technology wise, it’s not like these things would suddenly work well together. You’d have duplicate storage portfolios that’d you have to consolidate – good luck with that!

Also, Dell and EMC don’t really like each other. I have no idea about HP.

So, it’s hard to see what the value would be. Why would two of those entites together perform (make more revenue, more profit) better than if they were seperate? That’s what you need to ask. Acquisitions are risky and rarely work out well, so you’re taking on a risk. The payoffs have to be both simple and big. Anything else is probably gonna fizzle.

(You have no idea how hard it’s been to not type “synergy” as this is the one context – M&A where “synergy” an appropriate word and not some B.S.)

Like I said, though, you should never dismiss M&A rumors too easily if they’re reported by credible reporters. Crazy stuff happens and there’s all sorts of cloak and daggers that goes around.

I’ll take the big iPhone, not the giant one

After much equivocating on either side, I decided on the iPhone 6, with 128 gigs of course. I tried out both in the store and the Plus seemed just fine. It seems too fragile though and I know I’ll like the size of the iPhone 6. I’m moving from a iPhone 4s, so it’ll be big enough.

And, really, after two years, I can just get a big one if I want. It seems wise to pass on a first gen big phone. We’ll see what happens.

Lucky for me, my credit card company “detected” fraud, so I’ll probably have to re-submit the order all over. Huzzah! (How ironic, given the point of Apple Pay: I don’t think taking out cards is inconvenient, it’s the fraud crap that’s annoying.)

Fun & IRL

https://twitter.com/Rokshimmer/status/514106534956388352

  • Jousting on Bicycles – the reason I like “old” stuff like this is because it has that illusion of a time when we have relaxing figured out. If someone has enough time and mental capacity to come up with and execute such a nutty scheme, it seems like they’re living a relaxing life. Meanwhile, in contrast, it seems like contemporary life is a never-ending series of death-mark projects that are waiting to explode. Where’s my 5pm commuter train back to the suburbs?

  • I’ll be traveling a lot over the next few months and I’m sure I’ll miss some days here and there. Apologies ahead of time.

Coté Memo #042: “Is this helping at all?” and other Linkatary

Meta-data

Hello again, welcome to #042. Today we have 51 subscribers, so we’re +/-0. Keepin’ it smooth and level for the weekend! I’d love to hear what you like, dislike, your feedback, etc.: memo@cote.io. (If you’re reading this on the web, you should subscribe to get the daily email.)

See past newsletters in the archives, and, as always, see things as they come at Cote.io and @cote.

Sponsors

Follow-up

Tech & Work World

Quick Hits

  • Rackspace To Go It Alone, Focus On Managed Cloud – hey, at this point, Rackspace is fascinating to me. How will the sort it out? As TPM pointed out, the seem to have gotten their very own Magic Quadrant. I’m not actually one of those people who thinks Gartner operates like that, but it is awfully convenient – maybe because it’s a proper way to divide up the market. As we discussed in yesterday’s SDT, I have a big open question for cloud: is it the case that people want (a.) a converged cloud (a box they just plugin, not futzing with software and such), and, (b.) “managed cloud” as the “public cloud” version of that: Cisco MetaCloud, BlueBox, Rackspace, and every other “not gonna compete head-to-head with Amazon” vendor out there who feels the need to do public cloud (equation: IT – Amazon = what?). I don’t think “the market” is big enough to know yet, to have enough requirements to drive it. The vendors have to place bets and drive thought-leaderships. Good luck storming the castle!
  • Red Hat to Wall Street: I came here to chew FeedHenry and kick some ass. And I’m all out of FeedHenry – it seems like Red Hat has been doing well of late. I’m starting to think of “Mobile Backend as a Service (MBaaS)” as the new LAMP/J2EE-cum-JSP stack. We’ve changed the UI layer (from web to mobile) and you just need new a completely new stack of middle-ware because leaky abstractions. Think about it: if 70-80%+ of user were on mobile instead of web/desktop, you would just call MBaaS “middleware,” and the other stuff (web/LAMP/etc.) “legacy.” Private equity is on the prowl for the green screen – it’d be nifty if they started buying up old web stack companies.
  • What the winners in the application economy are doing differently – CA is doing well re-calibrating their marketing around DevOps (with some dusting of security-cum-API management). Here, they did a study that’s reminiscent of the 2014 Puppet DevOps study to try to show a connection between DevOps and “high performing business.” Looks like good raw materials for the field and keynotes at conferences that have the word “Expo” or “Congress” in them. (That’s a compliment.)
  • The more people fly, the more they prefer the aisle seat – I’m at 20,000 feet right now, brother. I’m totally that guy on this. Aisle all the time, baby: I gots to pee!
  • Life after Larry may be coming, but it’s not here yet for Oracle – it seems our 10 second analysis yesterday was a bit off. The 24 analysis hours cycle on Larry Ellison “stepping down” has been that not much is changing. OK; we’ll see.
  • Ping Identity Secures $35M Funding for Product Innovation, Global Expansion – “Series G.” The funding and corporate strategy history of Ping would be fascinating to explore. They’ve been around a long, long time (since 2002!) and seemingly keep just missing the brass rings of time. They’ve got to have rebuffed numerous acquisition offers, spent late nights trying to IPO, and done all sorts of other corporate financing gymnastics. Good luck to them this cycle! (If they get to Series O, can we call it “Series OG”?)

Fun & IRL

“Just call me ‘Captain.’ Mr. Dragon’s my father.”