Blogs

RedMonk

Skip to content

What ever happened to Cruise Control?

With the rise in popularity of Jenkins/Hudson, I’ve been wondering what happened with Cruise Control, the break-through project that helped bring continuous integration to programming. Charles Lowell of The Frontside tells us his theory.

In addition to viewing the video above, you can download it directly or subscribe to the make all podcast feed to get it automatically downloaded.

Transcript

As usual with these un-sponsored episodes, I haven’t spent time to clean up the transcript. If you see us saying something crazy, check the original audio first.

Michael Coté: So Charles, Jenkins very popularly used to be called Hudson.

Charles Lowell: Great!

Michael Coté: And yet there was CruiseControl. Why — I don’t want to say failed, but why — how did Jenkins, how was the space created that Jenkins took over from CruiseControl?

Charles Lowell: Well, let me start by answering the question with two words or talk two words but with one sentence, and then go on to expound for, I think, but you got your answer already. I think this thing just works when you like install it. You can download Jenkins and you’re up and running in about thirty seconds, whereas CruiseControl never was that. It was always a pain in the ass to get up and configure and blah, blah, blah and, I mean, I lost track of it.

But certainly while I was at ThoughtWorks, it started out as an ENDscript and a con job, right, and kind of snowballed from there and it was never kind of brought around from project to project and there was kind of good contributions from each place but it wasn’t ever — at least in my experience, a coherent project so much as an idea. And there were bunch of implementations on that idea.

And the thing is this, because it was for the people, it owned it, and in this case I’m thinking ThoughtWorks and ThoughtWorkers, it pretty much worked on —

Michael Coté: Quite a lot of extra —

Charles Lowell: I mean pretty much work but they were familiar with that. So setting it up on — at the beginning of each project wasn’t a lot of overhead in a grand scheme of things. It’s a couple three days or something, but you’ve done it a bunch and — so there’s no need to invest and package it so that it’s — so that it’s —

Michael Coté: So it wasn’t sort of like a product.

Charles Lowell: — that’s; yeah, it was never a product. I mean there was trend — it was, like you said, they were rumblings now making into a product, but I think that it was definitely more of an idea, and a very successful idea that was thought.

Michael Coté: Oh, yeah, yeah. That was — if I remember, it was, if I may use the word, it was kind of revolutionary in that sense, it was like oh, continuous integration.

Charles Lowell: Right.

Michael Coté: Huh.

Charles Lowell: Right. And so I guess that’s —

Michael Coté: And it just never evolved beyond that.

Charles Lowell: It never evolved into —

Michael Coté: — beyond a collection of scripts, as we would say, in the IT management world. There’s this distinction between, you’d get a bunch of products to monitor things, and it’s just a bunch of scripts. And then at some point, those scripts turn into a product.

Charles Lowell: Right.

Michael Coté: And I guess CruiseControl was sort of a downloadable thing that you could get up and running, but what you’re saying is it just didn’t get polished as well as later on, and then Hudson, then later we name Jenkins came in, and sort of polished this up.

Charles Lowell: And up and without having anything to build or anything knowing how to build it, you just —

Michael Coté: And there’s lots of other continuous integration tools out there, but that’s the one that you prefer.

Charles Lowell: It’s very — it’s pretty much to me just; can I use another buzzword “Zero Configuration”?

Michael Coté: Oh, yeah. Yeah.

Charles Lowell: You don’t have to configure a database.

Michael Coté: Did you know that?

Charles Lowell: — no dependencies; in the simplest case, there’s no dependencies, no configurations.

Michael Coté: Yeah. I think — did you know that Apple’s Bonjour thing was supposed to be called Zeroconf I think. But I think someone had a trademark on it so they couldn’t call it that.

Charles Lowell: Oh, is that what it is?

Michael Coté: — or something like that.

Charles Lowell: I thought Bonjour was Apple’s implementation of Zeroconf.

Michael Coté: Who knows.

Charles Lowell: Who knows.

Michael Coté: Bonjour!

Charles Lowell: Good evening!

Michael Coté: Well, thanks for the history lesson, Charles.

Charles Lowell: Yeah.

Categories: Agile, Development Tools, make all, RedMonkTV.

Links for June 2nd through June 8th

Disclosure: see the RedMonk client list for clients mentioned.

Categories: Links.

Running a mobile app shop – The Chaotic Moon Studios Story

I’ve been talking with mobile developers recently and over the past year. As my interviewee in this video, whurley, says, it’s a wide open space now with lots going on. While there’s lots of fragmentation (read: it’s not .Net vs. Java or even “it’s all web apps all time”), that’s actually an exciting thing at the moment.

This video interview is from Microsoft MIX11 where I ran into whurley. We finally say down to get the detailed story of what they’re doing at Chaotic Moon Studios, and what it’s like to be in the mobile app development business right now. tells us about the mobile app development and consulting shop he helps head, Chaotic Moon.

Transcript

As usual with these un-sponsored episodes, I haven’t spent time to clean up the transcript. If you see us saying something crazy, check the original audio first. There are time-codes where there were transcription problems.

Michael Coté: Well, hello everybody! Here we are at Microsoft’s MIX 2011 in lovely Las Vegas at the Mandalay Bay Casino and Resort.

William Hurley: Yeah, THE Hotel.

Michael Coté: I think that’s the full title. Yeah, it’s right, I always like, it’s THE as well, so you sort of emphasize it and —

William Hurley: You have to yell it out like THE Hotel!

Michael Coté: It should be italicized but that might be too much to ask. So as always I am Michael Coté with RedMonk. Can I have a — for those who have watched the program for years, I guess, a returning guest, would you want to introduce yourself?

William Hurley: Yes, my name is Whurley, I am the Chief Technology Officer of Chaotic Moon Studios.

Michael Coté: Which is a fine Austin-based company more or less.

William Hurley: It is, we are very attractive.

Michael Coté: I have come to know that you have locations spread out through the world.

William Hurley: Yes, that’s true.

Michael Coté: So why don’t you tell people what you know I actually found one of your cards that you left somewhere and I need to ask you later on where you got these great little things printed up here, very nice thick stock, you could almost cut.

William Hurley: Oh yeah, those were at the power charging station.

Michael Coté: There you go, you could almost cut like some cold butter with this, they are so like so stable. So why don’t you give us a brief overview of what you Chaotic Moon guys do?

William Hurley: So Chaotic Moon Studios was formed just a little over a year ago at South By Southwest. We launched the company, we do mobile everything. So we work with some processor manufacturers and help them patents and security related stuff, we work with phone designers like for actual hardware for phones and we do a lot of apps.

And recently we released a whole slew of apps at the last of 2010, beginning of 2011, two of which were the daily for Steve Jobs, Rupert Murdoch and Grover the monster for Sesame Street.

Michael Coté: I don’t want you to reveal the end of the book.

William Hurley: Which if you ask spoiler alert. Basically if you ask anybody, that’s kind of all we do, we were like, oh! You did daily? But we do a lot more.

Michael Coté: Well how many other apps have you guys worked on?

William Hurley: Oh God! Dozens and dozens and dozens, I mean we have done a couple of dozen Windows 7 apps alone that are already in the marketplace. We have I think 3 or 4 more that are going to be released in the next couple of weeks.

Michael Coté: And so I mean the most pathway you described what you do is mobile everything, and I mean one of the things I am curiously hear you talk about is what that is, like what it is to be a mobile development design whatever shop, because I think people are kind of familiar with like I am a web app shop or I am a Creative Suite guy that does graphic design and stuff. But there is this kind of new shop that is like what you guys are, which is you come to us for whatever you want on mobile. And like what does that look like?

William Hurley: So it’s specializing not in a vertical or in a special technology or whatever we are platform-agnostic, we are technology-agnostic. We specialize in mobile computing. So a couple of us came out, did a bunch of work at the pervasive computing labs at IBM, you know we’ve got — we are made up basically of two kind of components.

So X kind of big agency, big interactive agency, Pixars type artist, and then XApple and R&D engineers and project managers and stuff. So they fight all the time, and the secret to our success is we have heard each other just enough to turn out a great product but not to actually hospitalized.

Michael Coté: This would be the developer design collaboration, like Adobe use to talk about.

William Hurley: Right, well Ben Lam (ph) who is the co-founder and I, actually we are going to do a presentation we pitched at South By. We are going to pitch it every year until they let us do it. Everything is beautiful but everybody ruins it. So basically it was going to be like this kind of live mocking debate of developers who were like, you know, this is perfect in the architecture and everything, and then the designer wants to add like this thing and it like breaks everything and Ben was going to take the design philosophy and be like you know, why can’t you just have particle effects on everything, that’s not true, I like teasing Ben about particle effects.

Michael Coté: That’s right, why can’t these programmers do all their stuff in layers or whatever?

William Hurley: Right exactly, why can’t I export it from Photoshop to iOS code?

Michael Coté: Right, right, so as far as like this shop of a bunch of designer sort of interactive people and the developer people like how many people do you employ or how about the roof?

William Hurley: So we started with three, big question we get is like, who funded you, how did you start? So we started the company, three partners, no funding, we got laptops, we were firm believers that if you build software or you provide a service then you should do that, so as people, and it’s good and that’s actual business model, then we will pay the bills and make money.

Whenever we see a company it’s like huge, tens of millions of dollars of funding to build like apps or something. It kind of makes us laugh, I mean, it’s like, wow like, how’s that going to happen?

Michael Coté: And so I mean if we can like rabbit-hole on that a little bit, so would you say that you can self-fund yourself getting into the app business? I mean assuming you have someone to pay you to do the app, and then the implication there is that there is not necessarily like a value multiplier to make some stupid term up for getting like an investment, it’s not like I am going to give you $5 million, and boom, you are going to make $30 million.

(00:05:07)

William Hurley: Right, exactly, but that’s where – to come back, I am going to tie it into your original question, which is, what is this kind of like mobile everything, because we have this slogan, “All Your Mobiles Are Belong To Us,” it’s kind of like our little geeky joke, but it’s true.

So we do everything, we have done original titles of Microsoft Game Studios, for example, we’ve done original titles that have been featured by Apple, we have done big projects for big media corporations, movie studios and things.

We are doing, right now, we haven’t announced our partnership, we are working with somebody who makes awesome, amazing battery accessories and stuff. We are actually designs some new ones and some new products with them.

Michael Coté: So they are sort of industrial design you are doing, three-dimensional stuff.

William Hurley: Right, stuff you can actually buy at home, right? And so we are doing management and marketing and systems around, publishing systems and things like that. So we are really doing everything, and somebody we get a lot of comparison, somebody compared this to BASF, and they said, Chaotic Moon, it was a guy we were doing an interview in New York and he said, well I know who you guys are, you are not the guys who build all the cool mobile stuff I use, you make all the cool mobile stuff I use cooler.

And I thought for a minute like, we should steal that, it’s pretty good analogy, sir. But that’s kind of true, but we also do a bunch or original stuff. So mobile everything, we believe all computing is going mobile and you and I, as older gentlemen, have heard this for years-and-years throughout our career but it’s never been true. It’s like, I remember being on a project back at IBM in 1997 where it was like next year, it was like the year of the mobile and it’s coming at anytime.

And it’s taken a while to get here, and so what we want to do is we want to help build the mobile ecosystem as a lot better computing paradigm than the computing paradigms we have now. What I don’t want to see is all of the stuff go from — we don’t want to take all the PC stuff and be like and now it’s on a phone and now the screen is smaller. We want to really change things and we saw a great demo today, the Qantas Demo and the Keynote, which was exactly the kind of stuff that Chaotic —

Michael Coté: If I remember, it’s actually sort of telling you, you are probably not going to make your flights and suggesting. I mean add on to this or correct me if I am wrong, but it seems like a big realization of mobile UX design is focusing a lot on work-flow, if you will, rather than having a suite of functionality, I am thinking about one sort of path that someone goes down to.

William Hurley: Exactly, so all these things we do, from hardware design to accessories, in the battery life to apps that talk about the management of the phone or they give you some functionality of some feature, you have to do all of these, you can’t just be like, I do apps or I design industrial design, you have to do them all, it has to be a cohesiveness if you will to that experience. And as you know from system management world, the big system management players they compete on comprehensiveness, precisely, and that’s what we are doing.

So could be a your one-stop shop for everything, but we also work with a lot of other shops, I mean, somebody said once that we are not building a company we are building a cult, because they were trying to bid something out with somebody they thought was a competitor of ours or like actually we help start those guys.

And they were like, what? And then it’s a comprehensive approach, it’s a very all encompassing deal. Again the Qantas Demo I think really summed it up, it’s an airline app that told you, hey, I see you are on a schedule for flight and it’s coming up, and it’s about an hour before, and GPS as you were nowhere near the airport you are also not moving, you should get your a** over there, or here are some other flights you can use or I can click and deep-link in the directions. That’s a great example of kind of mobile computing if you are on a flight.

Michael Coté: Right, and so, I mean, just as a definitional thing like obviously mobile means smartphones, iPhones and Android, Windows Phone 7 —

William Hurley: Oh it means more than that.

Michael Coté: — yeah, and so like what — when you are saying mobile, I mean other people use phrases like edge devices or what’s the jobs being termed a non-pc or something like that.

William Hurley: Yeah, there’s something in the middle.

Michael Coté: Right, but give us an idea of the set of what you mean by mobile computing or devices?

William Hurley: Okay, so we do do things with network operating systems, we do obviously big focuses on mobile smartphones, and not just smartphones but phones in general. If you go overseas, I will be in Bali next month and there won’t be a ton of smartphones, but there will be a ton of phones, and in those areas of the world they use them for commerce and trade minutes like their money and do all kind of things.

So that’s also a big mobile space, and that’s actually a very big on tap market in our opinion. But we are also working on some research projects, for example, with an automotive manufacturer for heads up displays, in mobile computing like in-car computing stuff. So basically we would define mobile as it’s computing, you take with you or that goes with you when you are in transit, you are putting it in your pocket, you are driving from Austin to Houston, you are on a plane.

(00:10:05)

Michael Coté: I mean it almost seems like computing minus desktop, laptop and server.

William Hurley: Right. Part of — those are the three things that our computing and–

Michael Coté: Yeah, and pretty much everything else that is probably somehow a computer and also on a network to some extent is — I mean although —

William Hurley: We have some TVs in our labs that run an operating system that allows you to write apps and widgets and things for them. But we don’t really consider that mobile; we consider that more as we do servers and PCs which is all the stuff you do on mobile has to be able to tie into all of these other things you already have and you already do.

So if you are going to have an app on your TV, may be it gives flight status or something like that. You are going to want a way to have that information you did when you are in the car or sitting at work or whatever that you brought home with you transfer to all of those devices in your home and stuff.

So we do look at a larger ecosystem. We need to just focus on being kind of the mobile experts.

Michael Coté: So looking at that mobile space, if you will, like as a whole like, to ask a broad question, how would you characterize like what’s going on there? Like what’s kind of the like the top 3 things in there that are exciting and then who is trying to like move in on to it? Like what’s the landscape of like Apple and the handset makers and the Android?

William Hurley: Well, I think it’s a really interesting time to be a consumer. That’s my answer, because I think we have a couple of different shifts that are going on and one of those — [Cross Talk].

One of those situations is kind of this rise of Android and don’t get me wrong, we do a lot of Android development, love these guys of Google, but at the end of the day, it’s like what’s really driving that?

What’s really driving that is Apple won’t license you their OS and Microsoft and another companies traditionally charge you for it. So if you are trying to increase your profit margin and there is a good operating system that has a bunch of apps on it, of course, as a manufacture, you can put it on there. So I think some of that.

Michael Coté: It’s sort of free, if you will.

William Hurley: Yeah, exactly. I think some of that is free to sell very well, but I think that what we are seeing is we are running a very dangerous course. You know you said, what are the top three things; there is one I am really, really focused on right now and that is this homogenization of applications. What I mean by that is there is something to be said for consistent user experience, but there is also something to be said on the other hand for cheating users.

As an app developer, I have 2 or 3 phones on me right now. I have all of these different tools, all of these things I use and one of the things that I have a real respect for is users don’t get all those devices; they don’t get devices for free, they don’t get developer kits and cheaper license. They save all their money and they bought one device that they can buy and it’s iPad 2 or Google Zoom or whatever the case may be, you know, a webOS tablet, whatever.

And the thing is this they are sold a bill of goods when their best buy, wherever they are buying it, there is a little sheet that says here are the features. This has much faster graphics and all of these processing and everything. As developers what I am seeing mobile developers do is we are not saying great, we are going to take the Coté App or the RedMonk app and we are going to exploit the crap out of it on that platform. And by the way, it will be different than it is on iPad and the manufacturer will love that because they will say hey, this makes us different, the app does these extra things, it runs better, whatever.

And there is a bunch of reasons to do that about who would love it because of that, but at the end of the day, it’s like that’s delivering value to that consumer who bought that because they thought like, well, the graphics are going to be smoother when I play Angry Birds, faster when I do the 3D game. And what I see is HTML5, which we are big fans of, it’s not a ratified standard, but we support it, we use it in a lot of things. But one thing we don’t use it for is, for saying okay, we are going to get the Coté or RedMonk app and now it runs on everything and there is one code but you’re seeing it and it’s like because we have seen —

Michael Coté: See, the right ones weren’t run anyways. It’s a 14:03 platform.

William Hurley: Right because we are old guys and we have seen this story before and before there was all of the stuff, there were things like Java and there were other things that were like oh, are you just going to do it this one way and then everything looks other way. And it’s like, it doesn’t really work out that way and there is a variety of reasons; political and social and economic and everything.

Michael Coté: Sure and things like that.

William Hurley: Yeah, exactly, but at the end of the day, the one thing that I really harp on and what I am seeing is I really fear that the homogenization of these apps that in the effort to get a consistent user experience, you are actually cheating users out of the ability of really exploit these devices. You know I can give you a great example. Microsoft showed off the Pins today. They pin things with the information, the info tabs.

Michael Coté: That’s like pining web apps to the Windows Desktop or what?

William Hurley: Well, to the front, so that they can pin like the Qantas app of some of the others they showed. Okay, but I can’t do that on iPhone. So why would I homogenize it? So, well, nobody gets that feature because I am only going to do the lowest common denominator and things I can do across all fence. That’s a fantastic feature and if I can do it, yeah, I absolutely should because the person who bought that Windows Phone, they heard all the things at the keynote today and they bought it because they are like, hey, I am going to be able to get access this information in this way or the deep linking.

(00:15:11)

And I see too many people as developers not implementing those types of features that are platform-specific because —

Michael Coté: Yeah. Well, I mean as you keep saying, we are old guys, but I do feel like even for the young guys, there is a part of the culture that exists in developers where you try to avoid customizing per platform and over the years, that’s become something you would not suppose to do. And yet in the mobile space, it definitely, and you probably have a better sense of this than I do as you just went on about, but it seems like it’s kind of the opposite of that like, in fact like you —

William Hurley: I think mobile almost dictates that you have to do that. You have to say.

Michael Coté: You want to do everything native, if you will, or more stuff than you would think.

William Hurley: Yeah, you don’t necessarily have to do everything needed but you have to look at the frameworks and the tools that are provided. So okay, I am designing the app.

Michael Coté: I guess in this context, native means something specific. It’s more that as you are saying you want to — you shouldn’t be afraid to take advantage of an API that only exists on one platform, whether it’s a web or a native like code they were in.

William Hurley: The seatbelts in the plane with 16:17 home on is different than the one in our car is different than the one in the — it’s special. And it’s kind of the equivalent of saying, we are going to just have a seat belt, it goes across your lap, it’s awesome and there are reasons that we don’t do that. There are core reasons like automobiles; the three-point harness was designed for very specific reasons and there are contextual reasons like the environment you are in. You don’t need a three-point harness in a plane because the reality is if that plane has a really big problem, you know what, I am screwed.

If you have ever heard Bruce Mau’s Massive Change, he has a great thing on planes about how everything inside the plane is designed to give you the illusion of safety and security, we are doing something that you should never do which is riding on a big tank of fuel at 100 miles an hour, but it’s like that. I mean it’s yeah, I think mobile dictates that we start really saying, we are going to push our processor as further as we can. We are going to push our graphics as far as we can. We are going to push the platform that interface how people interact with it and we are going to do it in the context of the user doesn’t know that oh, well, that’s that way because it means it also works on the Windows Phone 7 or on the Android or on the bada or on the MeeGo.

They just know that you know this is the way my things worry, this is what I bought — this is what I was sold on.

Michael Coté: Alright and to your point, I mean vendors would love that, everyone would — people who have something to sell would love it because it gives them differentiation point.

William Hurley: Sure, absolutely.

Michael Coté: And then in theory, if it’s done right, consumer should like it because it gives them way too much choice, a lot of features.

William Hurley: It gives them the value they were promised. Again, we have spent a lot of time working with retail establishments and working with people who are buying phones and we have a user group and I get to go shopping with some people and be like what’s attracting, what you are liking about this, what are you doing and they always go to that like, the best part is they always jump down to that little thing and they are like, oh, well, that says it’s faster and it has more graphics. I mean you hold them up and you put the same app and you are like well, what’s the difference.

And they are like, I don’t know, like I don’t see it. And then in lot of cases, there are things you can’t do that with but in those cases, you can — and by the way, you will get better performance sticking with the frameworks, you will get a lot better support from everybody involved. And I think you will make a better product and by the way, it’s harder and it’s more expensive. Yeah, it’s too, but doing things right often is.

Michael Coté: So I mean if there is sort of a gradient of swings over here and then customizing to each platform that’s over here, I mean it sounds like you would push it way over towards customizing the platform.

William Hurley: Yeah, we are more over on it, but again, we are talking about the apps. People often confuse in mobile content with apps. Content — absolutely, you can use HTML5. There are absolutely, very cool things you can do with that. You can use a use a lot of JSON and XML and all of these things.

So we are not saying like oh, everything if you are on iOS has to be in a coordinated database. We are not saying that everything has to be in the new SQL databases that they had showed today that’s going to be coming out that’s built into the phone OS.

Michael Coté: Yeah, I think I mean it’s more just like you shouldn’t be afraid; in fact, you should explore using things that are unique on each of the platform of the phones or whatever it may be.

William Hurley: Exactly! The web is the great common denominator programming mechanism, I mean it is and we are having more seemingly browser wars happening right now like we have already lived through two or three times.

Michael Coté: Sure.

William Hurley: And it’s like yes, you should explore that, you should find out what’s unique about that platform, you should find out what is going to make that user experience really, really special and it’s going to be something super simple. And the super simple stuff is always something that’s hidden way down in the SDK that everybody overlooks and nobody talks about a keynote, you are like, oh, that is the best feature.

Michael Coté: Like what would an example of a super simple thing to be from the past or something that you would make up just to give people a sense?

(00:20:00)

William Hurley: Oh, I mean, I think — I’ll tell you. I think, again, I mean I hate harp on what we saw today here at Mix, but I really think that the deep linking into an app, into a place in an app is fantastic. Now, that’s not HTML5 or web stuff. It’s taking from app, but it’s is built into the native thing and we heard it here. But when it comes out, how many developers that weren’t here are going to go digging through documentation and find out, oh, I can actually take you to a stateful point inside my app to a specific screen. I think it’s an incredible feature.

Michael Coté: Yeah, I mean it did seem nice because you don’t have to navigate to that point. I mean to use the web terminology; it saves your clicks to get to somewhere.

William Hurley: Yeah, exactly. And that’s what I am saying is it’s not an either/or. It’s the right mix of both, and the right mix of both is very crystal framework on the device you are working on, because they are written for a reason; there is a SDK for a reason.

Michael Coté: Yeah.

William Hurley: You kind of stay there and there is very good engineering reasons to do that and then mixing in the HTML5 and the cloud services and the things in the right mix, that’s really where you end up.

Michael Coté: Yeah.

William Hurley: I don’t think we are going to have a 100% completely all apps are native or hey, all apps are HTML5 as much as many of the web designers and people that we have met here that we would probably like that to be there.

Michael Coté: Yeah. Now I mean it is also interesting because like on the cloud side, it’s kind of the opposite, like everyone wants to go towards homogenization or commodity stuff and really make there be one backend.

William Hurley: Is that what you mean; on-demand?

Michael Coté: Yeah or utility computing, whatever you want to call it. But it is kind of the — because the bad servers started out being exotic custom hardware. I think it was specialized and now it’s trending towards the opposite of what you are saying, and it is happening on the — or like that you like on client side where you want the clients to be specialized and take advantage of things. So it’s a nice flip-flop of what’s in the —

William Hurley: Yeah and I mean at the end of the day, you are talking about providing valuable software. You are talking about providing value to users, and each case is going to be different and each app is going to be different. But you have to start taking an approach of putting yourself in the user’s shoes. I recently got in a little bit of a tiff with a person, Mr. “Maddog” at 22:19.

And it was about, he gave a great example of how he was an end user and why the GPL was so great. And he said that he’s done his resumes in the same software for 25 years and he got to a point where he couldn’t do what he needed and he didn’t want to reformat it. He went, because the code was GPL, he found it, he downloaded the source and he fixed it and he recompiled it and he finished his resume that night and it all took four years.

Michael Coté: Alright!

William Hurley: You, sir, are not an end user. And that’s the problem with everybody that’s going to watch this, it’s the development always. We think about — we are like well, everybody does this.

Michael Coté: Yeah.

William Hurley: We often fix things that are trivial for us to fix and it’s a two-hour support call for somebody who got their phone at 23:05 Wal-Mart or whatever.

Michael Coté: And I mean that points to all of my friends who are called upon in their family to fix computers. Over the past few years, they forced all those people to buy Apples. They are like, if you want help first, you buy an Apple and basically, their service desk requests sort of speak go down, because a lot of the stuff is just, it’s simple, I guess.

William Hurley: Well, we forget what people are trying to do with the devices and one of the things that I like everybody in mobile to steal from the Windows Phone 7 Campaign is this concept of like technology should do something for me.

Michael Coté: Right! Right!

William Hurley: I don’t want to have to learn to use it. I don’t want to have to be forced to do it, and I think everybody in mobile should just take that and just run with it and do their own versions of it. Again, not too hard from the Quanta thing, but that was a great example of not having to do anything to have technology go, oops, more than a calendar alert, I am watching you, know you are not in the right place, know you need to be here, making some assumptions and doing some things that are very valuable that deliver a lot of user value to me in one, two clicks, I have already corrected the whole situation. I think getting off the value and you are ask for a couple of things. The second thing I think we need is we need faster networks in the worst way and apps started small, and now they are getting big. I mean it’s you remember downloading eight megabyte apps back in the day and you are like, oh my God! It’s 12 megabytes.

Michael Coté: I plugged into the Ethernet here at some point and it was like 30 down and 40 up or something which is, I understand, in Korea, that’s nothing or whatever.

William Hurley: Right.

Michael Coté: But for here, it’s phenomenal, like it’s mega fast and it is — there is a problems with the networks speed.

William Hurley: You take your phone and you walk through the hotel or the casino and you can’t get a call or get a signal, right?

Michael Coté: Yeah.

William Hurley: It’s like as computing loser, so you know the first thing is avoiding the homogenization.

(00:25:02)

The second thing is infrastructure; we need better infrastructure and better latency and fault tolerance and all of these things that need to be taken into account.

Michael Coté: Yeah, that was like earlier this week, Cisco said they are kind of like cinching up their belt and getting rid of the Flip brand and things like that and I was thinking like that’s fantastic because what I would really like now to do is just make networks faster. But I don’t really care about video conferencing and collaboration; I just want faster networks.

William Hurley: You don’t want to work with anyone else.

Michael Coté: That’s right.

William Hurley: You just want to work faster by yourself, because if you could, you could do the work of 10 or 15 people you would have worked with at a slower network speed.

Michael Coté: And then I could keep being a hermit. Are there other like missions you would like to see the mobile space go on? You had two there, I mean what else? What are the other guiding principles you are operating under at the moment.

William Hurley: Well, I think that there needs to be a lot more imagination, I mean a ton of apps, I was really disappointed, and apologies to Microsoft, but if you look at the board over there next to the left of us right now on Windows Phone 7 thing, there is all of those apps and there are all apps that we have already seen and done. I loved the keynote today, and it was great they did the USAA app, but I didn’t understand what the difference between it was and the one that was 26:24 on other platforms literally like quite some time ago.

Michael Coté: Right. It’s more that they ported — I mean it was basically an app where you can – it’s funny like it exposes archaic process that need to be updated, but you take a real physical check and write the check, and you take a picture of the front and back and then you can digitally send the check which is great.

William Hurley: Well, or you could deposit, I mean USAA is an amazing institution and it has some phenomenal developers; Michael 26:48 incredible guy, but they — you could have given me a check and I can do that. So I mean I thought that the way Microsoft 26:57 should have been like Coté gives Whurley a check and Whurley goes, I am not driving to the bank, snap, snap. And it’s amazing, but the thing is I am not harping on that one at all. There are so many things that have been done. It’s like, wait, this is a brand new platform. But where is the like, here is this cool app nobody else has done that on any other platform because of all these cool features. And it’s like everybody is a little too focused on making money; they have all got the gold rush 27:26 on every interesting platform.

Michael Coté: Yeah, but there is like a feature in — I guess, Android has this too, but in Windows Phone 7 that the iPhone definitely doesn’t have it and you probably know the name of it, but you basically, — you can add little extensions of things. Like send this photo to Flickr, whereas by default, you can always send it to Live or some crap.

That would be an interesting thing to think about is like how could have USAA insert themselves into that workflow. Like where are areas where it would — I don’t know if this makes sense, but you know where are areas where it makes sense to take advantage of that or the notification stuff and pining things. But it’s true; I mean it gets back to the first thing you were saying.

William Hurley: Well, let’s face it; everybody is doing the bare minimal they need to do to get an app where they get into the —

Michael Coté: You want to start with small successes so that you can get on to bigger ones.

William Hurley: Right, but they never go on with bigger ones and we are kind of the opposite as a company. I mean we did The Daily and some of the other things we’ve done are huge risk. They are the first of this and the first of that, first Apple subscription app, the first tested that system and the first publishing infrastructure of its type and so on and so forth. So I think you know we’d like to see other people joining us and taking a lot more risk and putting the credibility on the line and sometimes it works great and sometimes it doesn’t.

But you do nicer things for users; you improve the user experience overall, you pioneer things, you do a lot and from mobile to really get to the dream that kind of Neal Stephenson or William Gibson type utopia that we think mobile computing will be. We really, really need to focus on pushing the boundaries and limits. Now is an incredible time to be a consumer and just because of all other choices that are coming out, but it’s even more incredible time to be a developer because all of the choices you have and all of things you have been doing, you don’t have to do at all platforms like we do.

You may focus on one, you may focus on a certain thing within one, but there are so much opportunities. There are so many really, really cool things and I am just not seeing enough of them out of us or anyone else.

Michael Coté: And like on that note like what — when people would ask for sort of like a justification of satisfying all that opportunity like basically a business case, if you will, I mean what do you tell them as far as like here is the monetary opportunity that should motivate you to want to pursuit these opportunities because people are hopefully in a healthy way always paranoid of technologists coming and telling them like give me some money so I can do cool stuff.

William Hurley: Right and that’s the thing. Sometimes you know we talk to customers and that’s we have incredibly honest conversations with them and sometimes it is you were doing this because you have to because your competitors did it and sometimes you are doing it because it is just a really cool thing. It’s almost a PR stuff.

(00:30:03)

And sometimes it’s very, very, very good business fundamentals. Now when we spec out jobs, we always put a section on Return On Investment and sometimes that may say, you guys are crazy, you are not going to get any money on that. We are expensive and you are nuts, but sometimes customers look at that and say, well, how do I justify this from a monetary standpoint, and it’s if you are selling an app for $0.99, rarely are you going to make a lot of money and we have this illusion.

Michael Coté: Sounds like especially if they are ahead of you guys.

William Hurley: That depends if their goals are making a lot of money, we are going to architect it to do that. But the thing is, is you take there are some really successful apps out there that have tens of millions of downloads. So let’s just pick a round number and say, 100 million downloads over the life of an app, average app is updated quarterly or so. So take that and say it’s been out for a couple of years. So really, you have may be 10 million actual downloads and then you take a certain percentage of those to about 18%, what we find is people who had it, deleted it, somebody else got it, they got it back.

So it’s just started changing it up. So people think that if somebody has made a $100 million on an app and it’s like if that was not the case, if that was the case, we would all be doing it. I wouldn’t be sitting here and talking to you or building apps for people.

Michael Coté: Sure. Sure.

William Hurley: I would just be making the original titles myself and we have done some original titles that have been really successful but these are not — even something that is a top selling app in any other stores is not necessarily the kind of blockbuster you think it is.

It’s marketed that way by everybody in the ecosystem because they want more developers and want more apps because that’s what drives — it’s not about the phones; it’s about the apps and the consumers.

Michael Coté: Yeah, now I always tell people is there and I don’t know if people catch on my careful wording, but there is an incredibly important perception that you can get rich writing mobile apps and maintaining that perception is like what’s important to fuel like enough people–

William Hurley: And the fact is, is that if you actually took the time to do it right, there is a lot of money out there, but it is like you don’t get to —

Michael Coté: Like you said earlier, yesterday is expensive and it is hard, like I guess doing something well isn’t always just easy.

William Hurley: One of our biggest operations in our business is the service called Application Resurrection and that’s where you spend a lot of money, you spend your kid’s college education and your company’s budget of ever building an app and it didn’t reach the matrix and it didn’t sell what you thought and it didn’t save the resource and you just dump all of that to us. And we take it behind the curtain, we have a conceptual artist who re-envision it and then we take it and we redo all of the art and all the development and everything and we release it, sometimes under the 32:34

Michael Coté: Oh, you guys are the clean-up team.

William Hurley: Well and that’s one of the biggest areas of our business because so many people are just like in such a hurry to make all of this money that they hear about out there, but there is a lot of crappy apps. I would argue that we used to have this argument out like well, between Mac and Windows, Mac had fewer apps that were of higher quality and Windows had thousands of crap apps. I mean it’s like well, surprise! Now their shoe is on the other foot because it’s like now there are tons and tons of apps out there where it’s like really good download, a hundred of them just randomly that you have never heard of are – look at the bad ratings and see how many stuff is just thrown out there in the hopes that maybe they will do get on to make money and then I’ll end up doing it right.

Michael Coté: There’s lots of resurrection thrown to the wall, by the way.

William Hurley: Yeah, you have to do it right the first time. You have to do it right the first time.

Michael Coté: So last question and it’s you have been really luxurious with your time so I appreciate that. So someone wanted to start a mobile business in the context of everything we’re starting. Never mind the tech — well, not so much of technological choices, although maybe that’s the most important thing but with your success and experience over the past years, like what would you advise them, like what’s the important thing to start doing when they start it up?

William Hurley: They should call me and I will help them. I mean we have been started helping several mobile companies start. We have been incredibly successful and we are taking that success and we are sharing it in the form of a, investing in mobile properties. So there are several apps that our companies that we’ve now helped out. We have invested either time or money or a resource or all three. There is a bunch of people. So somebody that you and I know who should go unnamed at South Bar 34:14 said, I am on TV, and he said, you can’t be a system lord if there is no system, can you?

And he is right. So we put on a 34:21 on him. But the reality is, look, for us to be successful, things have to make it over that kind of tipping point. To do that, there have to be a lot of other people doing this and it’s in my best interest to help.

Michael Coté: Yeah, I mean this is a very open source community sort of idea, I mean to generalize it.

William Hurley: No, but that’s how we put. We are a very open source company. So all the helping people, call us, we may invest in you. You may be like, we are going to start a three-man desk shop and we are like, great! We have got work; we will help you get that started.

Michael Coté: I mean so to generalize it, it seems like the advice here would be that at this point and hopefully, at future points in the mobile market that it pays off to be friendly and promiscuous with people. Like hiding away and being isolated is less helpful than if you just sort of talk with people and try to collaborate with other people.

(00:35:08)

William Hurley: If you have come from open source and understand open source, you will be very well in how we see the mobile ecosystem and where we see it going which is it’s like a lot of people compare us to ARM, because ARM sells to everybody their suites or what, and we are kind of that way. We don’t really see anybody as competition; we may work with them, they may need us. We see it as a much, much bigger thing and we are going to work with Google, we are going to work with Apple, we are going to work with Microsoft, we are going to work with Samsung and HTC and dozens of others and we are going to do the best damn job we can every single time.

Michael Coté: It’s sort of like no one is your enemy. They are all potential friends or collaborators.

William Hurley: Well, it’s even a little more different than that and maybe a little simpler. It’s each one, there is an opportunity to do something newer and cooler than you did last time and that’s what’s really driving our success is always like treating ourselves, like a lot of people have this kind of rock star thing going on. And just like a rock star, once the last album is out and like the initial sales are done, it’s like you are only as good as that and further that goes back without doing something new and big then it’s like you know what I mean.

Michael Coté: So it’s like second piece of advice that always answer what have you done for me lately.

William Hurley: Yeah, that’s true, exactly. So it’s like be very open, be very honest, I mean there are so many opportunities. People often are afraid of the limitations and they are like well, they tell people that they won’t hire me. It’s like you don’t know that; they may not need you to do that. There are tons of these very low level and mid level opportunities that have low hanging fruit that are a great place to start getting it to mobile as a developer.

Michael Coté: Yeah, yeah. Well, great! Thanks again for taking all that time. It was good stuff.

William Hurley: I appreciate it. It’s good to see you again.

Michael Coté: And we will see everyone next time.

Categories: Conferences, Programming.

Tags: , , ,

Automating People Back into IT – Presentation from #Know11

View more presentations from Michael Coté

How can new technologies and practices like cloud, social, dev/ops, activity streams, model-driven automation, JavaScript injection, and rogue developers make IT better in staid organizations? That’s the question I tackled in my Knowledge11 talk, above. I wanted to go over some general and some pointers for how these new technologies can make the role of people more important, valuable, and efficient.

The them of people and IT is one of my favorite. For me, the most important thing new technology can do is make the role of people more important. Usually, people are the ones who figure out how to best make a company money and then make sure the execution takes place. Also, you know, I want to keep The Robots at bay (I for one, however, would welcome our new Robot Overlords, should they arise!).

Disclosure: ServiceNow is a client.

Categories: Agile, Cloud, Conferences, Ideas, presentations, Systems Management.

Tags: , ,

Building the Knowledge11 Portal on-top of the ServiceNow Platform

Who’d have thought you’d hear about server-side JavaScript programming in the context of ITIL and service desk? That’s exactly what we get in this interview with John Roberts of ServiceNow. We discuss how they built the Knowledge11 portal on-top of the ServiceNow stack. You can use your imagination to see how this might map to other PaaS development on service-now.com.

For a wrap-up of the Knowledge11 conference, check out my trip-report.

Transcript

Michael Coté: Hello everybody! Here we are in lovely San Diego at the Knowledge11 ServiceNow User Conference. And as always this is Michael Coté with RedMonk. And I’ve got a guest with myself. Do you want to introduce yourself?

John Roberts: Sure! I’m John Roberts. I’m a developer with ServiceNow. I’ve been with the company for almost four years now. I started the first couple of years in professional services and now I’m in the development team.

Michael Coté: So around this, around this conference, you guys came up with the Knowledge Conference Portal.

John Roberts: Yes.

Michael Coté: Usually for a conference, you have things that list the sessions and things like that, but can you give us a sense of what the Knowledge Conference Portal is, what purpose it’s serving for the conference here?

John Roberts: Sure! First of all, a little bit of background. Last year, Knowledge 10 Conference, our CMS platform was kind of the bigger announcements or the new features, the CMS plug-in allows us to build customized user interface and not have to settle with the interface that we give you by default. So people have used it to style their own instance to look like their corporate website and things like that.

Michael Coté: All right.

John Roberts: So in Knowledge10, we were announcing that platform and so we really wanted to showcase it, and we thought what better way to showcase it than make our Knowledge Conference Portal built on top of our CMS platform.

What makes a platform so nice to build on top of, I want to add a new table, I want Knowledge Conference agenda records; I want meet an expert records. The platform itself makes it very easy to build this platform up into an application. So we didn’t have a conference management application, but we knew the data types we wanted; and just like a customer would in their own instance when they want to have a custom application for their business, we just decided what does a data structure look like? Let’s build a table to house all the session information, what are the schedules, who is running it? And then the same thing with the expert; what is a simple data structure? We need an expert, we need a time, and we need an attendee to be able to book it.

So in all of that we leverage the same technology that our customers have access to, to build out custom applications very easily. And then again we use the CMS platform to just present that in a prettier format.

Michael Coté: If I was building some other thing on top of the ServiceNow platform — I don’t know, arranging who can take out the golf carts that they have in this lovely resort here or something, scheduling a resource like a golf cart…

So it sounds like from the way you’re describing it, I don’t know if this is the only way, but a way to start is that you basically define the data model if you will – the tables.

John Roberts: Yeah, what information do you need? What do you want to store? would be the first thing? Once you understand what do you want to capture for information, it’s very easy for our admins to — customer admins even — to build that table structure. You don’t have to understand a lot about database models, you don’t have to understand database language; all through our user interface, you can define, I need a table name and I want these field names on it.

Michael Coté: Right.

John Roberts: And then you just start filling out the forms just like you would with any other record in the system. So it’s relatively easy to build out that data structure.

So then the next step would be, like you mentioned, what do we want to do with that data. And there is a number of ways we have automation we can build onto the backend of the system, and then we have user-facing automation. I need a button on this form to do something; I pull up a golf cart and I want to book it. I’ve built a button to mark it as reserved, something like that.

Michael Coté: And then that might be a field in the table row that’s like —

John Roberts: Yeah, is it booked or not.

Michael Coté: Yeah. Charlie cart is reserved or whatever.

John Roberts: Yes.

Michael Coté: I don’t know what the name of the carts here. Is there actual like programming that you’re doing, like code that you’re writing, or is it more wiring things together or what is —

John Roberts: It’s a little bit of everything. So in the simplest case, if you want a very simple application, you can perform some of this functionality or the logic that drives changing the data structure with really no scripting. We have things like UI Actions and UI Policies that make it easy to define logical changes through the user interface without having to script too much.

But most people that’s simple model really doesn’t do a lot for them, so we have a variety of ways where people can script changes to the data structure. So we have both. We support server-side and Web-based client-side scripting to manipulate the data.

Michael Coté: And then what’s the language you guys use for that?

John Roberts: It’s JavaScript.

Michael Coté: So you run JavaScript on the server and the client side?

John Roberts: Yes.

Michael Coté: Oh, yeah, yeah. Now that makes sense; I mean there’s — with things node.js and things like that, like there is this crazy renewed enthusiasm for JavaScript on the server side. I remember I evaluated the Netscape something or another that ran JavaScript on the server side, and people said that was madness, back in the late 90’s or whatever.

But it’s fun to see. What I like about that model is, if you can get over the fact that it’s JavaScript which for older folks this is sort of like shocking, I guess. It’s like people wearing short-pants or something…

John Roberts: Yeah.

Michael Coté: But it does seem like you can have like one language on both sides, which is sort of crazy to think about.

John Roberts: Right.

Michael Coté: It’s sort of like the UI wins over the backend almost.

John Roberts: Yes.

Michael Coté: Is there like an IDE that people have or like where does it actually take place?

John Roberts: It actually takes place right inside the application, right inside of the normal user environment that the end-users are performing their function in. The admins have a slightly different view and access to more of the behind-the-scenes records, the configuration records.

So once an admin logs in, if they wanted to define say server-side scripting actions, they would use a business rule typically that processes that logic against one or more records. So through a business rule form, they would have access to a script field. And in there they would just write their script; it’s not an IDE interface, it’s right in the application.

We do have some support for which objects are available and that’s one of the areas we’re improving right now to make that — the script fields a little more intelligent so maybe we have some context where we could do some type ahead, and what methods are available on a certain object. So we’re trying to make that a little bit smarter.

Michael Coté: Continuing part of the portal that you built, so I imagine the agenda then there was some mixture of retrieving those events through some service from the database.

John Roberts: Right.

Michael Coté: And then doing some JavaScript and HTML and stuff to render it. I mean just basically render the table.

John Roberts: Yes. That’s exactly it. So we’ve got the CMS that allows us to write an HTML front-end that doesn’t look like our application, the standard application. We’ve got the agenda sessions sitting on the backend database, and through our normal interface, we can certainly display that list of sessions. It just doesn’t look as pretty in a CMS; we wanted to really make it look like an HTML website, not a list within our application.

Michael Coté: Right.

John Roberts: So what we basically did in this case, we had to do some customization, some of it’s a little more advanced and something we call a UI page, where we leverage XML files using Jelly language that allows us to render data on the backend, configuration, and output that into HTML format.

Michael Coté: So generalizing this is a little bit, it seems like this is basically the way that you would customize anything in ServiceNow. You’re using similar ‘patterns’ is the wrong word, a similar approach, if you will.

John Roberts: Absolutely, yeah, it is. One of the other areas that’s kind of interesting still in the Knowledge Conference Portal is our automatic provision of instances, which is pretty interesting. So all of the lab sessions that we have, we give all the attendees their dedicated instance that they play with, so people aren’t stepping non each other’s code. And we provision that through our own Run Book Automation which we also launched last year a little bit, more formally this year we’re really getting heavily into it.

We’re also leveraging the Amazon EC2 Web services to run these instances. We just didn’t have the server spaces to spin up a thousand instances for every attendee.

Michael Coté: Right, right.

John Roberts: So why not leverage the cloud that’s already has that type of capacity. So also through that the Conference Portal, users can go in and say, I want to attend the scripting lab, and within 5-7 minutes, we send them an email back that we just provisioned your own instance right on the cloud for you that you can start to use.

Michael Coté: Right, so you kind of built up for a little application within the portal?

John Roberts: Yes.

Michael Coté: I guess to mix a bunch of words together, people are requesting that, and then are you actually linking some sort of JavaScript calling out to Run Book stuff or like what — I’m interested in what the chain is there because this might be one of the only instances where JavaScript is used for anything remotely related to IT management?

John Roberts: We’re pretty much using JavaScript to control all of the IT service management, anything in the application.

Michael Coté: Right, right.

John Roberts: But in the case of our Run Book Automation and the instance provisioning, it’s actually quite a complex workflow that we’re running through. I saw the map of it and there is a lot of steps, communications with Amazon cloud — I want to make this request, I want to copy this master, and give me information back on what’s the URL that I can actually connect this to.

Michael Coté: Right, right.

John Roberts: So there is an awful lot of logic behind the scenes that our Run Book Automation team has been very busy setting up. And we’re happy with the performance, the 5-7 minutes.

Michael Coté: Yeah.

John Roberts: And if you ask anybody else, how fast can they get their application running, dedicated for me just for the day to play, and seven minutes is pretty impressive.

Michael Coté: There’s another thing that I noticed that’s in the portal — you’ve pulled in — you guys call it Live or Live Stream. It’s basically a stream, if you will, and it’s kind of a mixture of an idea of an activity stream and a Twitter stream and all these things together. You guys have that in the portal as well, you have an instance of it in the portal.

And I’m curious — it’s another good example of how you — no one uses the term “mashup” anymore — but you’re mashing up these various things from the ServiceNow platform. So can you go over how you integrated that into their portal?

John Roberts: Sure! One of the new features we just added was social IT services, so we have a chat feature that’s built in the system now and we also have this live feature, so Live Feed is what we’re calling it. And basically it’s kind of like a Facebook, Yammer social environment that’s dedicated to the instance; so probably more along the lines of Yammer which is protected, private to the corporation.

So we have that in the application now that we’re shipping in the next release. So we wanted to really showcase that this year in the Knowledge Portal. So we have that available through the portal, and any of the attendees that are registered can go ahead and have a communication, they can create their own, essentially chat groups; it’s really not a chat, but a live feed type group that they can house their messages in and have these discussions.

And the other thing we wanted to do was just to try to trigger more activity, was to pull in tweets from Twitter that have certain tags, like our #Know11, our tag for the conference. We wanted to display those in the Knowledge Portal in Live, so we built an integration from external services such as Twitter to Love Feed so we can display those.

Michael Coté: Oh the sucker stuff in there.

John Roberts: Yeah, yeah. I think the term somebody calling was ‘tweetsucker’ which I kind of like.

Michael Coté: Well, great! Well I appreciate you spending all that time to go over that. I think it’s always nice to — when there is a — to use the general term, when there is a platform available to be programmed, it’s good to have some pretty good — some reference examples.

John Roberts: Sure! Yeah.

Michael Coté: Otherwise you’re just like, oh, I can do any thing you want, and that’s really not helpful.

John Right: Yeah, it doesn’t get you very far.

Michael Coté: Definitely! So I appreciate it.

John Roberts: Yeah, I appreciate the time too!

Disclosure: ServiceNow is a client and sponsored this video.

Categories: Cloud, Conferences, Enterprise Software, RedMonkTV, Systems Management.

Tags: , , , , ,

DevOps & IBM, with Pete Marshall & Peter Spung – IBM Rational Innovate 2011

The practices and technologies of DevOps have begun to spread into what I’d call “the mainstream,” which is fantastic: DevOps has a lot to offer to all IT organizations. IBM has taken notice and started getting involved. Here, while at the IBM Rational conference Innovate 2011, I talk with IBM’s Pete Marshall and Peter Spung about DevOps is and what IBM has to offer.

Transcript

Michael Coté: Well, hello everybody! Here we are in sunny Orlando at the Rational Innovate Conference in 2011 of course. And this is Michael Coté of RedMonk as always, and I have got two guests with myself. Would you guys like to introduce yourselves?

Pete Marshall: Hi! I‘m Pete Marshall from Tivoli. I am in the Strategy Group.

Peter Spung: I’m Peter Spung from Rational, also with the Strategy Group.

Michael Coté: So what we have here I think is sort of like a meet embodiment of a trend going on at the moment called DevOps. On the left we’ve got the Dev and on the right we’ve got the Ops.

And so I have been talking with you guys a little bit about DevOps and just — I have been talking with everyone about it, so it’s fun to have you guys here to talk about it. And I am curious, rather than me ramble on about DevOps, what are you guys seeing is sort of the challenges that are impelling people to look into integrating development and operations together more? What’s driving this interest in DevOps?

Pete Marshall: Well, I think the interest is getting driven from a number of areas. I mean, people are seeing what’s going on in the web space, they are looking at the Flickrs of this world, the Googles of this world, and they are saying, yeah, can I do some of that? Can I do continuous integration into production? Can I get my development operations people working together? And how do I go about doing that?

And especially, how do I do that in an enterprise environment where there is a lot more going on? There is a lot more legacy code. There is a lot more moving parts. There is a lot more entrenched organizational structure. So there are some big challenges there, but I think the rewards people are looking for are great.

Peter Spung: The moving parts really resonated with me when Pete said that, because when you think about it, not only the applications that get deployed and used on the web as he was talking about or generally in an enterprise have a lot of moving parts and a lot more keep bidding at it.

In fact, there was a stat I saw the other day that in 2010 half the server deployments were virtual, not physical. So we have crossed this threshold where more and more the server deployments are virtualized instances, not physical boxes. So the number of moving parts keeps going up.

Organizations, are getting more-and-more complex, lots of off-shoring, lots of globally distributed enterprises all over. So it’s just getting more complicated. People need to be able to integrate these capabilities and functions, and people that get the work done in order to deliver the capabilities they need.

Michael Coté: That definitely sounds kind of like the enterprise take on DevOps, where you have complexity because it’s necessary, not because it’s sort of like an albatross hanging out on your shoulder, but it’s what you need to run your business essentially, and whether it’s geo-distributed or just a lot of complex moving parts in software.

And I wonder, as sort of an example of the benefits that you get to, I mean, do you guys have some interesting examples in that, whatever you want to call it, big or complex or enterprise, some examples of DevOps or DevOps-like things being successful? Like what’s a way that you can tell people, here’s why you would go through the trouble of learning about this DevOps thing and adapting to it?

Pete Marshall: Well, I mean, we’ve got one customer in the financial services space that’s bringing together its asset management for both software and the infrastructure. And what they are finding is, more and more they are just making savings in time and deployed assets, because they know where things are. They can go out confidently, do a deployment, do things quicker. Really get time benefits, cost benefits, that space.

And are they doing that a 100% across everything? Absolutely not. Doing that in a very small part of a very large enterprise, but they are getting good savings out of that already.

Peter Spung: We’ve got another client who is — basically they are a workforce company, they place employees into different jobs. And they had an application that was actually core to their business, a portal that’s used for the direct interaction of the employees with the managers and placing them.

And this employee portal, they were having all sorts of availability problems; crash, they were having problems diagnosing where the issue was, couldn’t figure it out.

So they put some integrated solutions in place, some frameworks, some automation, a whole bunch of tools offered by both Rational and Tivoli to solve this problem, and they increased their uptime dramatically, and they are looking to deploy this to more of their applications.

They felt — the framework they put in place in DevOps was not only one about tools and infrastructure, it was also about culture. They did a whole lot to break down the barriers between the development and operation organization, and get people collaborating and working together towards shared goals, keeping this portal up.

Pete Marshall: Culture being probably long-term, one of the biggest benefits you get out of this. If you can break out of this mold of, it is development and our job is done once the code is tested and then here’s the CD or a set of files, go forth and implement it. Culture change is interesting.

Michael Coté: Yeah. I mean, it’s definitely something that I see, and kind of when I am evaluating if something is DevOps or near DevOps, it seems like — it does involve a fair amount of organizational or a cultural change, or some amount, I don’t know exactly how much.

But more importantly, the kind of technologies that facilitate that and make that change possible, because there is always a back and forth between the way an organization is structured and the technology that enforces it, and it’s just a loop that goes around.

And along those lines, I mean you guys were getting to some of this, but I wonder if you could give people some guidance when they are thinking about doing DevOps or evaluating different options like, what are the kind of things they need to be looking at to trust that it is a DevOps thing? Like how can they establish trust with the offerings?

Pete Marshall: That’s a really good question. I think what you really need to look at is this — is this change in terms of a process, in terms of people, of culture as you were talking about. I think that’s a very important thing.

I’ve seen projects where we’re going to do re-tooling but we’re really going to keep these things separate. So look for shared outcomes, right. What are you actually trying to do here, if you’re just trying to improve technology or you’re just trying to improve results in operations, results in development, that’s great. Maybe you’re doing virtualization or automation, cloud, maybe you’re doing Agile on the development side, but really you’re not doing DevOps. DevOps is going to smell like DevOps, it might not be able to point and put your finger on what it is, but you’re going to see those changes happening on both sides. If it’s not, you’re not doing DevOps in my opinion.

Peter Spung: I would agree. Give it the sniff test and then make sure that it’s capabilities that span both development and operations. So it’s during planning, planning applications and scoping them out and architecting them. Can you architect the infrastructure, as part of it, right? Can you think about what’s going to be happening in deployment? Can you design for that? Can you design for run-ability, sustainability, in the manufacturing term, let’s say design for manufacturing? That’s sort of concept. Does it transcend what’s going on inside development?

You mentioned looping back, which I think is a really important notion. Once things are deployed, can you build feedback groups, that feed back information from operations back into development? Trouble tickets flowing back in defects, performance data flowing back into test automation, and test suites, that kind of stuff. Can you establish those linkages? Can the vendor show it? Call us in, call any of our competitors, and let us demo it for you. Let us set it up and do a proven technology.

Michael Coté: Yeah, that feedback loop is one of the things I like the most just because I feel like it gives developers insight into people using their applications they didn’t have before or at least a lot more easily and quickly. This data was always out there but I think there is a lot of effort in DevOps to lower those walls down and to be metaphoric about it.

Peter Spung: Yeah.

Michael Coté: So finally, we’ve also kind of hit on some of the things you guys are thinking and I am guessing they’re kind embodied or embedded if you will in IBM offerings. So I’m curious like what it is that IBM has to offer at the moment in the DevOps area? If one of those people wanted to come to you guys and ask you to, show us what you’ve got, like what would be the kind of things that you would put in front of them?

Pete Marshall: Well we’ve got a whole set of integrations between the Rational and the Tivoli tooling. We’d cover everything from deployment, integration of defect and problem management, integration of the data layer, the assets and CMDBs, change management. As Peter is saying, some more applications that get into things like enterprise deployment planning, governance, that kind of thing.

What we find is that we take these to our customers and everyone wants to do something slightly different, I don’t think there are any cookie-cutter DevOps projects at least in the market today and we’ll engage. So folks who are watching this video and who are here at Innovate come and talk to us, and if not, give us a call, get in touch. We just put a new Collaborative Development and Operations website up on ibm.com, under both Rational and Tivoli URLs, and you should come and check us out.

Peter Spung: And you’re asking this fundamental question, I think, about what claims can clients believe, and how should they test the vendor making the claims? I’d say do it, test them, I’d also say look at the particular attributes, like how consumable is the solution. Are there multiple, what we call entry points? What customers would call bite-sized, accelerated pieces that they could take on and accelerate a solution for them, and get that done. As it based on open standards, is the way the integrations are done, open accessible that other vendors can play.

We have an architectural movement and I’d call a de facto standard called OSLC that we’re working on. It’s an Open Interface, it’s got about 365 registered people in 34 companies interacting with it. Basically building out specs for integrating requirements management, change management, quality management, all those sorts of things.

So ask the vendor, is this open, is the way you’re integrating something I can extend, is it something that other vendors in a large ecosystem can play in? Those are important attributes of a solution that client should ask the vendors about, and we’ll stand by what we’re doing I think.

Pete Marshall: Probably we will, absolutely.

Peter Spung: Absolutely.

Michael Coté: Well great! Well, I think it’s been nice to see you guys as a large supposedly ponderous company, kind of pretty quickly move on to doing something in DevOps. So it’s been nice to see that you guys have actually you have something to offer people at the moment, and I really appreciate your spending the time to go over what you guys see as DevOps as useful and how it’s being used and then more importantly what you guys have at the moment to help people out.

Pete Marshall: Yeah, it’s an exciting thing, it’s an exciting time, it really is.

Peter Spung: Yeah, we are in it for the long haul, we’ve been doing it for like five years now, and we’ll be doing it for ten more, I’m sure. It’s a big problem and it’s complex, and we’re happy to be part of it, contributing, making stuff happen in the industry. And thanks for the opportunity to talk.

Michael Coté: Yeah definitely, we’ll have to check in next year and see how it’s turned out.

Pete Marshall: We’ll do that.

Peter Spung: Super!

Michael Coté: Well, we’ll see everyone next time.

Peter Spung: Thanks Michael!

Disclosure: IBM is a client and sponsored this video.

Categories: Cloud, Conferences, Programming, Systems Management.

Tags: , , , , , , , , , , , ,

Links for May 27th through June 2nd

Disclosure: see the RedMonk client list for clients mentioned.

Categories: Links.

Cloud = Speed, or, How to do cloud marketing

I’ve sat through, probably, 100’s of presentations, talks, papers, and marketing on cloud at this point: it’s been several years now. There’s a huge variety in the marketing messages, pitches, and explanations for what cloud computing is and why you, dear CIO (or are you?), should spend time and money on us for your Cloud Experience.

After all this time I’ve come up with a theory for cloud marketing: cloud is speed. Everything else supports that simple, clear message, and anything else is distraction and marketing-bloat.

Pardon me as I get hyperbolic to explore the theory here – I explicitly call it a “theory” because I don’t think it’s 100% solid and it definitely doesn’t apply across the board…but let’s pretend for awhile that it does.

Cloud marketing tactics

If you accept the theory that cloud is speed (which we’ll explore below), that means several things for your cloud marketing:

  • You start by telling your audience that once they start using cloud, they’ll be able to do apply IT to business (make money, more than likely) faster.
  • That speed means not only that you can pursue opportunities (another word for “money”) faster, but that you can fail faster and thus, “fail towards success” (or “iterate”). If failure is “cheap,” you can use it as a way to learn what success is.
  • The point of doing all this cloud stuff is to make things faster: if we can’t prove to you (with past case studies and projected mumbo-jumbo) that our technology makes your IT service/software delivery faster, we’re doing the wrong marketing.
  • You have to build enough trust to have the audience ask for more – you’ve got the gain the benefit of the doubt for a very doubtful message. More than likely, no one is going to believe you: every wave of IT has promised to make things more “agile,” cheaper, and faster. If it worked, why are we here with all this opportunity to speed things up? (Never mind Jevon’s Paradox for now.)

Of course, if you’re of the “every great argument needs an enemy” mindset, that implies another straw-man you need to depict.

The problem with IT is that it’s slow

In order to buy more IT, you must connivence people there’s a problem, and that it can be solved with what you have to sell. Here, the problem is that traditional IT – “legacy” if you want to be aggressive – is slow by nature. There’s nothing you can do to fix it by addressing the symptoms, you have to change the core sickness. To put it another way, “cloud dusting” won’t work: you’ll end up with the same boat-anchor of IT with just a different management layer on-top.

This is a point Randy Bias makes relentlessly, and rightfully so. Him and the CloudScalling folks have been wiggling-up a more nuanced, pragmatic argument that exposes the costs of the “legacy cloud” vs. the (my words) “real cloud” that’s worth checking out.

Again, racing to the simple message: cloud is speed. How fast does it take to deploy a new release, IT service, and patch, provision a new box, and so on with your “traditional” setup? How fast does cloud allow you to do it? If a marketer doesn’t immediately prove that cloud is not just faster, but dramatically faster, the whole thing is off.

You want something like this chart from Puppet Labs:

Once you speed up IT, you make more money

Slow IT means the business has to move slower, both missing out on opportunities in hand and missing out on the option to spend time developing new opportunities. If I, as a business, can try out a bunch of different little things quickly and cheaply (see below), I’m not “trapped” in my current shakles of success: “that new idea is all fine and well, but do you have any idea how long it’d take to build it up to even try it out? It takes 4 weeks and $100,000 just to keep them to add a new field to our order form!”

We’ve used the term “business/IT alignment” in this industry a lot over the past few decades. It sounds awesome, and powerful, and like big bonuses: the CEO actually depends on me to help make money…and it works! Business/IT alignment has meant many things when it comes down to the details. Here, it means one thing: speed. By using cloud (the marketing message goes), we can actually respond fast enough to be valuable to the business.

Does this hold water? A survey from Appirio last Fall seems to answer “yes,” at least, you know, among the people who answered:

Have these expectations been realized in actual results? Cloud adopters report that they have. More than 80% of companies that have adopted cloud applications and platforms say that they are now able to respond faster to the business and achieve business objectives. They’ve also found these solutions easier to deploy and cheaper to maintain. The cloud has helped change IT’s role in the business—70% of adopters say that IT is now seen as a business enabler and 77% say that cloud solutions have changed the way they run their business.

(What’s novel about the Appirio survey is that they asked people who’ve already been using cloud stuff, not just what people are “planning” on doing, which most cloud surveys ask – it’s worth submitting yourself to Appirio lead-gen funnel to get the PDF.)

What about cost?

EC2 means anyone with a $10 bill can rent a 10-machine cluster with 1TB of distributed storage for 8 hours. @mrflip

Costs are a type of friction that slows things down. Having lower costs is table stakes, and if your cloud offering isn’t at least affordable, it’s going to take longer to catch on. Once something is cheap, I can do more of it, more frequently, meaning I can try out more things, explore more options, and – yup – move faster.

If I can spin up a super computer in hours rather than months (or minutes!) for thousands rather than millions, I can achieve a huge amount of speed because I can do more, at lower cost, more frequently. Lowering costs for the sake of lowering costs is only valuable for IT when there’s nothing new gained with the new technology. “Commoditized” IT is what fits here: x86 boxes, email without Enterprise 2.0 bells and whistles, backup software. As a counter example, notice how Apple is able to build up brand to not do that: also notice how “closed” their whole brand ecosystem is.

Controlling costs, then, is something that support speed. If cloud was the same price as traditional IT, or more expensive, it would slow down the rate you could use it (unless you have unlimited budget, e.g., spies, scientists, and other past customers of super-computers).

(There’s a sub-argument to be made that lower costs “democratized” the technology, like open source did the Java application servers and middle-ware, and later software development in general. But, at this high-level, that’s details for further discussion.)

Building trust so you can get to the boring stuff

The most important thing you need to do for cloud marketing is to make people actually believe you. The goal is to get the benefit of the doubt enough to be asked to speak for a few more hours on the topic. The stretch goal, if you’re a public cloud thing is to get people to trust you enough to sign up for the service, for example, to try the Opscode Platform trial, do some “Hello world!”ing on Heroku, putter around on GitHub, or just mess about in EC2. Sadly, most people with high dollar cloud stuff to market don’t have that luxury as they’re selling private clouds, which require, you know, the usual PoCs and such, if only in hardware acquisition and network/security setup. Appliances can go a long way here, of course. But, back to that first goal: being asked back to further educate the prospect.

While cloud gasbags like myself may bore of the whole “what is a cloud” talk, when I talk with the cloud marketers in the trenches, that’s a whole lot of what people want. What exactly does your vision of the cloud mean and how does it apply to me? And let’s be frank, if you, a high paid marketer are involved, you need to sell big-ticket, transformative projects, not tiny things (marketing to the masses is an entirely different set of tactics). This isn’t a cynical, “a sucker is born every minute” take, it’s realizing that if IT is to be a core asset for business, it’s going to be a big deal. The Big Switch hasn’t happened just yet.

How can you build this trust? First, focus on what’s different this time. Explain what has changed technologically to make this speed with cloud possible. Again: “agility” is something IT is supposed to do and everything laughs at. Here are some stock, “what’s different this time”‘s:

  • New options are available: Amazon, Rackspace, GoGrid, and all the other public clouds are new, different ways to run IT. They’re fundamentally different: we’re not just installing magic software on-top of it, the way you manage the hardware, the datacenters, the network, etc. is different.
  • Moore’s law has delivered: infrastructure is cheaper and faster (and somehow outpacing Jevon’s Paradox, I guess – though certainly not on my desktop!)
  • Once you move to this new model and change the way you develop and manage applications, you can start doing things differently like Frequent Functionality (delivering smaller chunks more often), observing user behavior (a million one way mirrors), and other useful killer features.
  • Thanks to consumer web apps and the iPhone-led renaissance in smart phones, people don’t expect IT to suck as much. It’s the old “if Facebook can do it so easily, why can’t the IT department.” This trend is important, because it means there’s demand for IT to suck less – put another way, they have a reason to change – put another way: rouge IT is a very real competition, see that ticker symbol CRM.

There’s more, of course: but to win the benefit of the doubt, you have to explain why it’s different this time, why it will work. All you want to achieve is getting asked back for more and if you can make them believe that cloud is speed, they might just ask for further discussion. And, it of course helps to no end if there’s plenty of examples, but you don’t always have that luxury.

Everything else

Obviously, there’s more details, but I want to keep the theory simple: cloud is speed. Once you go down that rat-hole, the other valuable things like dev/ops, the types of applications you drive on-top of cloud, how you change your deliver model, and where your offerings fits in on the SaaS/PaaS/IaaS burger all come next. The biggest argument of all is over public vs. private. The idea that you need private has all but won, with “security” and special snow-flake concerns weighing too heavily on decision maker’s minds.

But all those things come from what you, the marketer, is actually trying to sell beyond simply speeding things up.

(Here’s some more details and rat-holes in lovely mind map form for those who want to dig deeper.)

Disclosure: Puppet Labs, Opscode, and others mentioned above or relevant are clients. See the RedMonk client list.

Categories: Cloud, Marketing.

Tags:

80legs – What's in Your Stack?

How do you develop and run a grid and data-mining on-demand service? That’s what we find out in this installment of What’s In Your Stack, with 80legs. And if you’re interested in telling us about your stack, feel free to just fill out the questionare!

Who are you guys?

I’m Shion Deysarkar, the CEO of 80legs, a web crawling and data collection services provider. We have three lines of business, all supported by the same stack: custom web crawling services, data feeds, and a large “general” crawl of the entire web. Most of our business centers around delivering and discovering structured data on the web. This data includes everything from social data to business listing data to meta data (e.g., where all the PDFs are).

We are working on extending our stack even further. Right now our stack looks like this:

  • 50,000+ grid computing nodes
  • Grid control servers
  • Web crawling control servers
  • Crawl job submission application

We are extending it to this:

  • 50,000+ grid computing nodes
  • Grid control servers
  • Web crawling control servers
  • Crawl job submission application
  • document storage system
  • document search/processing application

These extensions will provide us and our customers with a complete end-to-end system for searching and retrieving structured data from the entire web. So if you want to run a query like “create a CSV table of all florists in Texas with at least a 3 star rating.. oh, and tell me everyone that has been there as well”, that will be possible here.

How would you describe your development process?

We have weekly iteration meetings each Monday where we discuss:

  • Tasks completed last week and any challenges faced during them.
  • Tasks to be completed this week.
  • Overall company issues.

Developers are fairly autonomous within their task assignments.

What’s something that has worked well for you guys?

The weekly iteration meetings have gone very well for us. We started this practice about 2-3 months ago, and it has really helped us keep a steady pace as far as deliverables. It has also helped shape our culture toward efficiency and productivity.

[Across the board, quick frequent meetings seem to be extremely effective for development teams. The “stand-up meeting” seems like one of the quickest to value tools that Scrum provides. -Coté]

What development (IDE, build tool, etc.) and project management tools did you guys use, if any?

  • Pivotal Tracker for task assignment.
  • Google Mail/Calendar and Skype for communication.
  • Eclipse and SVN for development.
  • Ubuntu for server OS.
  • Apache/Tomcat for web servers.
  • Dell 1U and 2U servers for local data center.
  • 50,000+ personal computers for grid nodes.

Have you guys considered using git and/or GitHub?

We looked at GitHub a while back, but since most of our guys were familiar with SVN, we went that. I think at this point it would be too much of a hassle to switch, and we don’t see much benefit at this point. It would be nice to take advantage of the community on GitHub, so we may have a separate public repo there for public code.

What do you use your local datacenter for?

The local data center consists of 2 racks that manage crawl job submission and our distributed grid. We require a fairly small data center foot print given what we do thanks to the grid architecture.

Through our investor (Creeris Ventures), we have access to deals since as a whole Creeris companies do a decent amount of server purchasing. So we can get a couple thousand knocked off listed prices, etc. We have had some issues with hard drives, but we do put our machines through the ringer, so maybe it’s to be expected.

Disclosure: GitHub is a client, as are Dell and Canonical.

Categories: Programming, What's in your stack?.

Tags: ,

Links for May 25th through May 27th

Disclosure: see the RedMonk client list for clients mentioned.

Categories: Links.