Coté Memo #082: Disrupting with high prices, indulging in colonialism porn, and dying among the tomatoes. Oh, and Docker!

Come to the Austin Docker Meetup this Thursday (Jan 7th) to see me and some much smarter people talk about “The Container State of the Union.” See below for some of the “prep” work I’ve done. Also in this edition, new types of disruption theory, compliance in DevOps, books, and an interesting link round-up.

Tech & Work World

Resetting Prices

Disruption theory follows a template: a new competitor starts with an inferior product at a lower price, finds success, and eventually takes over the market from the leaders. “Inferior” here means less features, capabilities: something that’s less appealing. At least that’s the interpretation that seems to win every 2-3 years when a big debate about disruption vs. Disruption comes up.

As an example, you can see some advice on how FitBit can win against Apple:

Zino, who maintained a “hold” rating on Fitbit shares, said the company should focus on products that cost less than $100 and have an intense focus on wellness.

A FitBit watch would be cheaper and less featureful than an Apple Watch. And that brings up the interesting point, as it’s the Apple Watch that’s “disrupting” FitBit, Jawbone, and all the others.

There’s a clutch of companies now-a-days that use high-end offerings to suck up market-share from low-end competitors, Apple being the chief among them. In this model, you start with a more expensive, usually more featureful offering (though not always, sometimes it has less features in the name of design elegance!) and, more often than not, don’t really lower your prices much. Instead, you seem to “rescue” lower price expectations, “resetting” the price. iOS devices are an example here, of course, but I think the pricing of other things – like public cloud and SaaS, depending on how you slice it up – are good examples as well.

You can see Uber doing the same (they started off as a black car service, after all). If you’ll pardon my lazy-lack of researching, it feels like there are others who do this: my own company, Pivotal, arguably is doing this in the application development space (our products are far from cheap, but we’re capturing a lot of market-share).

Let’s look at Apple more as an example: all their hardware is much more expensive than alternatives, and sometimes even has less features! That’s confounding in itself. There are times when Apple is more expensive and has more features, e.g.: the Apple Watch definitely has more features than a FitBit or an analog wrist watch. Again, Uber is an interesting example: they started at the high-end and are now going down-market. Maybe Silver Car is in the same bucket.

I’m not suggesting this cancels out Disruption theory at all, but like the Exponent.fm boys often suggest, it seems like there’s a different type of disruption on the rise that isn’t talked about enough.

You can do all sorts of business theory gymnastics to re-define the job to be done to make Disruption theory work. Horace Dediu did this very well, long ago, in his analysis of the iPhone: it’s category was the PC, not the mobile phone which brought with it some of my favorite charts ever (see an updated version of the concept that better highlights the amazing growth of iOS).

Along those lines, usually, the cult of “big d” Disruption shuffles this type of “beyond Disruption” thinking off as “sustaining innovation,” which just means the industry improving their existing offerings and businesses. I’m sure that’s often the case, but I keep thinking there’s a new model in there somewhere.

On the other hand, I get the feeling that if I had some actual numbers and 3-5 other industries to look through, all of this would seem kind of silly. Another good trick is to look at market-share/revenue vs. profit. Again, Apple is instructive here: they may not always take all the revenue, but they seem to dominate in profit. It’d be interesting to run this kind of thinking versus Amazon Web Services and the trail of dead that have tried to compete with it. I have no idea what kind of business theory explains all that.

Dealing with compliance in DevOps

For my column last month-lyish, I wrote up some tips for dealing compliance and audit people when you’re “doing the DevOps.”. These things really apply to any type of cloud-enabled IT, mostly. As ever, I think the main points are: if you talk with people more and really understand what they need, then go understand your tools and what you can do with them, most things are achievable.

Check it out, I’m curious to hear how you deal with this stuff. It comes up all the time, and the answers are usually not very concrete.

Container State of the Union

I was asked to be on a panel this week for the Austin Docker meetup: it’s this Thursday, Jan 7th, 6pm, at the Rackspace Austin offices. My role here – other than trying not to shill too much for Pivotal – is to be a pretend industry analyst…I think. You may recall I tried to sort out WTF “container orchestration” was back in 2014 with CloudSoft. That’s pretty much what I’ll have to do; as dedicated readers no, I have no idea what I’m doing…but I can PowerPoint the shit out of any unknown!

Speaking of, here’s some fun-facts I’ve gathered so I can hopefully shuffle through some big, blue index cards like a nervous person:

451 Research on Container Adoption

  • Above, my old colleagues at 451 (Jay and Donnie) have a good way of looking at container adoption: 21% of surveyed people are doing something with Docker, 6.3% in production. That’s n=991 from their 1Q2015 Voice of the Customer research.
  • Run on 6% of the hosts DataDog monitors, n=7,000. “At companies that adopt Docker, containers have an average lifespan of 3 days, while across all companies, traditional and cloud-based VMs have an average lifespan of 12 days.” (DataDog, Fall 2015.)
  • Earlier in the year, New Relic said that the average life-span was 3 minutes, across 300 customers “using an aggregate of 40,000 to 60,000 containers daily.”
  • Anecdotally, in most all of the customer visits I go on or hear about, Docker is on the short list of things to look into. Obviously, companies don’t always end-up picking it by far (451 only had production use at 6.5% above…but plenty of experimentation): Pivotal Cloud Foundry had a run-rate of $100m/year based on 2015Q3 numbers, so plenty of cash in this small market is going to alternatives. We’ll see how it pans out.

Anyhow, come check it out the panel if you’re in the area!

Shameless Self-promotion

Books

Over the Christmas break, I finished up some books…and started new ones:

Quick Hits

A lot of time has passed since the last memo, so there’s more links than this. As always, follow my links in Pinboard or Tumblr if you want more real-time junk to read:

Fun & IRL

“Cease to React At All”

If you are willing to look at another person’s behavior toward you as a reflection of the state of their relationship with themselves rather than a statement about your value as a person, then you will, over a period of time cease to react at all.
Yogi Bhajan

When I was studying Eastern philosophy in college, I had a strange relationship to Buddhism, Taoism, and all that. It seemed like giving up so much and disengaging with the world. The idea that the ultimate idea was not Logo-atic truth, but “nothing” seemed weird.

Now that I barely have time to contemplate what “nothing” even means, I value the idea of letting go a lot more. Somewhere between becoming self-less, table flipping, getting the kids ready for school, a fine bottle of bourbon and steaks at home with family, Vito Corleone dying in the tomatoes, watching the tech industry, and Courtney Barnett on repeat…is a pretty good place.

Sponsors

Meta-data

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