(I cross post my week-daily newsletter here, but also feel free to subscribe to it directly if you’d don’t want to follow CoteIndustries.com regularly.)
Meta-data Hello again, welcome to #29. Today we have 36 subscribers, so we’re +3 - 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.
Momentum at Constellation Research, customer numbers
That old pay to play model just doesn’t suit us. So this makes it hard to make it all work. We know it’s tough, but we also know it’s worth pursuing. We do have to thank over 100 sell side (vendor) and 200+ buy side (end users) clients. And to address someone else’s comment, these aren’t webinar attendees (we’d be able to list 1000 clients in that case) These 200 represent folks who’ve engaged us for subscriptions, advisory services, or attended our programs.
Cloud == speed, pt. 2, or, Developers moving at public cloud speed driving IT transformation
WTH: How do you see the path towards the software-defined Data centre?
AB: What I believe is driving this trend is that developers and organisations are looking to move extremely fast. Developers are getting used to the paradigm of going on AWS (Amazon Web Services) and getting resources immediately instead of weeks/months of provisioning time. That is the benchmark against which they are now holding their internal IT organisations.
The decline of Novell
I’ve been reading up on Novell’s history. So far it’s got some fascinating twists and turns. Wikipedia sums up the turning point well:
The inclusion of networking as a core system component in all mainstream PC operating systems after 1995 led to a steep decline in Novell’s market share.
That is, once networking become “commoditized,” the unique position Novell had with IPX changed. And then there’s some channel hijinks that happened.
In an API-driven cloud, Intigua wants to wrap APIs around your management midsection
A report I wrote on Intigua is up now. Here’s the 451 Take for y’all now:
Intigua has always been a company with a difficult marketing proposition, having started off as a packaging and deployment balm for systems management agents. While there is certainly utility to ‘managing the managers,’ a broader positioning and purpose was clearly needed. Intigua’s new positioning as an enabler of cloud management APIs looks encouraging, and if the company can extend into ‘orchestration’ as a consequence, it can start addressing one of the major gaps of large enterprises that are ‘going cloud.
How to be a hardware analyst...?
After reading an, as ever, great, deep coverage of some new fangled piece of hardware from TPM, I got to thinking: I don’t really know how hardware analysts approach their craft. What framing and context do they use to understand, evaluate, and judge any given chunk of hardware?
I’ve never been much of a hardware person (which was an odd strength while I was at Dell, being that I was there to work on software strategy).
Hardware is the price variable
With EVO, VMware is pitting the hardware vendors against each other for deals that will likely involve hundreds to thousands of nodes in large enterprises, and the competition will drive down hardware prices and therefore the overall price of the EVO solution. If hardware costs less than it might otherwise without such pressure, that extra margin can come from the software and support in the EVO stack.
It’s rough being a hardware vendor.
Coté Memo #28: Yet another DevOps landscape, webinar tips for analysts
(I’ve had a little email newsletter for sometime. It’s fun! People like it and write to me! Rather than rely on the archiving at TinyLetter, I thought I’d post the archives here. However, feel free to subscribe to the newsletter in its proper format, email…or just read it here, whatever you like.)
Meta-data Hello again, welcome to #28. Today we have 33 subscribers, so we’re +/-0. I’d love to hear what you like, dislike, your feedback, etc.
[audio cote.files.wordpress.com/2014/08/u…_010.mp3]
Summary
We discuss thinking beyond human error as Bill starts to summarize the book Behind Human Error. It’s always helpful to look at how the system and process caused the wrong move. Also, thinking about hardware, and some nice feedback from designers.
Subscribe to the feed: http://feeds.feedburner.com/UnderDevPodcast
Your friends @cote and @BillHiggins
Hardware, what is it?
- Coté is confused about how to think about hardware.
- The IBM “brain chip”
Follow-up on “design”
- Some follow-up from a designer: of course they iterate, dummy!
- The air hockey meat-mallet (actually called the “OXO Good Grips Meat Pounder”)
- Where Good Ideas Come From and avoiding the Ferrari to Pinto transformation.
- Design documentary movies: Objectified, Helvetica, and the upcoming Urbanized.
Human Error
- Bill goes over Behind Human Error, causing us to discuss how various pipelines (systems) in product management work in waterfall and non-waterfall mode.
- How do product managers fit in to a design-heavy pipeline?
Zenoss is on the hunt for large enterprises with a little help from Hadoop and Docker (451 Report)
Back in my RedMonk days, I spoke with Zenoss a lot, so it was nice to finally catch-up with them again. They’re moving up-market and adding spending much time beefing up their back-end to handle the resulting, larger scale demands for a systems management platform in the enterprise space.
The full report is available for 451 clients, but here’s the 451 Take:
Zenoss has been undergoing much change in recent years.