Front-end development with Rails, Visual Studio 2010 – make all #001

Update: I’d been pointing to the wrong audio file below (here’s the right one). Corrections have been made!

In this inaugural episode, I talk with the developers next door to RedMonk Austin (see picture above – Charles, Mando, and Daniël) about their use of Ruby on Rails as a front-end layer. We spend a lot of time discussing UI toolkit choices and customizing, JavaScript and Ajax coding, using rails as sort of glue-layer to their UI, and heavy GUI development. Additionally, we talk about Pivot and Visual Studio 2010.

Download the episode directly right here, subscribe to the feed in iTunes or other podcatcher to have episodes downloaded automatically, or just click play below to listen to it right here:

Transcript

(I haven’t checked this transcription in detail, so if you notice something funny looking, ask before assuming it’s “funny.” For example, everyone but me quickly devolve into “Male Speaker.”)

Michael Coté: Well, hello everybody! I thought I would embark on a new podcast generalizing from RA Weekly and I haven’t really checked the availability of these names yet but I am thinking I am going to call it Make All which is a little nerdy and retro and everything, and the idea is I just wanted to start a podcast where I can just talk about software and software development, sort of unrestricted by category.

So we will see if that name is available, if not we will come over with something else. But I thought for the inaugural episode, we would start here with — I guess you could call them my co-officers.

Male Speaker: Reporting for duty, Commander Coté!

Michael Coté: So here is the RedMonk Austin Office. We are right next to the Austin branch for Serial Solutions. And when they are not working on the next Blueberry’s competitor, they are working on a software that is used in libraries. They do a lot of development and there is actually three of them here now, usually there is just two. Why don’t we introduce people? Why don’t you start?

Charles Lowell: Well, my name is Charles Lowell and my mother is calling me.

Michael Coté: And this is the call that the clients have heard about. You actually are a very popular person on the iPhone, always getting calls, and yourself?

Daniel: I am Daniel. I am visiting Charles here at the office.

Michael Coté: You are from like the Amsterdam office, right?

Daniel: Yup, I am.

Michael Coté: And yourself?

Mando Escamilla: My name is Mando Escamilla. I am here with Serial Solutions. We are all focused on the UI side of our application.

Michael Coté: So like the UI that — so first off you are doing like library and stuff?

Mando Escamilla: Yeah.

Michael Coté: Or is it library? I never know how to say it?

Male Speaker: I have to spend much time in a library, so I can tell you the proper pronunciation.

Michael Coté: So what’s the technology that you guys are using mostly for the front-end stuff?

Male Speaker: So we focus mostly in Ruby on Rails as kind of server-side software and then lot of JavaScript, a lot of HTML, CSS.

Michael Coté: So when you are using Rails nowadays, like is it mostly like a front-end centric thing or do you have it like doing all the backend stuff? Are you like all the way down to the metal or you like Rails or is there other stuff that you typically innovate with nowadays?

Male Speaker: Yeah. So our application is probably a little bit different than most Rails implementations. Ours is a very thin layer on top of this, really big search engine backend. So we don’t talk to a database, we talk to this big set of solar indexes and these kinds of things.

Michael Coté: Like the Open Source project?

Male Speaker: Yeah.

Michael Coté: Right, that’s interesting. But you have sort of a non-relational deal in the backend if you will?

Male Speaker: Oh, absolutely. We don’t have users. It’s like if you go to your university and you search the library catalogue, you usually have to log-in for that. You just go up to a computer, sit in there in the library and you type-in.

Michael Coté: And do you think that’s common for Rails applications nowadays, like I mean, Rails has been around for what like five years now?

Male Speaker: It’s been five, yeah.

Michael Coté: I mean it kind of started out as like a — you had your database schema or whatever, there was some model and a database somewhere or in your head even and the point was like you would like spin up your magic Rails stuff and say oops! When you type things wrong and everything like in the screen cast and like boom! You would have your application, right?

It seems like there was a lot of contention in the Rails world along that it is a whole database like in the code it was great but it wasn’t always like fantastically performed and things like that. So I wonder like what you guys have seen the evolution of where Rails fits in the stack if you will?

Male Speaker: Well, that was always the magic of Rails, that you could start with your model, in your code, and then the Rails stack would come bark out your database schema, and create your tables and migrate them as you change them.

So you can work on solving the domain problem and that was kind of the big relation I think to a lot of developers about Rails. Nowadays I mean that’s still well, and good and true, but I think Rails has kind of started to fill in other areas of the development landscape.

It’s not just these kinds of applications. It fits in like with our stuff which doesn’t have a backend database. So we don’t use ActiveRecord which is the Rails ORM, we just don’t use it. We use RubyGems that we wrote to talk to our search API and it works just fine.

Michael Coté: So like when you are using Rails like what do you end up spending like what are the top three things you end up spending a lot of time doing like do you have to make like custom like webpage? Do you have to do a bunch of custom like JavaScript and Ajaxy stuff or is it sort of like the integration you spend a lot of stuff time in or like what is it kind of push you into as far as work you actually do? Like why do you programmers still have to do stuff when you are using Rails?

Male Speaker: I submit, I haven’t really used Rails for about four years now and I got pulled into this project, so I had to start all over again. But, I still think it’s very database-dependent. If you get the new Rails knowledge, you still need to do some stuff to have it work without a database.

That said, I spend most of my time on the JavaScript side of things, not too much on Rails. I have been doing Ruby straight up and haven’t meddled with the real framework that much.

Male Speaker: That’s true. We do spend a lot of our time either writing Ruby libraries that get called by a very thin layer within Rails itself, right? And then we spend a lot of time presenting that data in HTML and JavaScript.

Michael Coté: So we just say, you do more — the code work that you end up doing, end up being more not UI-centric, but like directly related to rendering stuff on the screen, or is it more of the — for the lack of a better phrase, it’s kind of like the middleware that gets to that point, when it comes to the JavaScript stuff that you do and the Ruby thing you do. Like you spend a lot of time like, here’s a great way to validate a block of text that works in the UI, or here’s like a way we lay things out. Are you doing UI framework coding or more like business logic you kind of coding?

Male Speaker: No, this is probably for our product — specific to our product. We spend a lot more — I spend a lot more time worrying about the presentation side and we just get — we have these kind of magical data structures that come to us from the magical end of the API.

Michael Coté: Oh, yeah.

Male Speaker: And we have to massage it every now and then.

Michael Coté: Yeah, yeah.

Male Speaker: Very light on the business rules.

Male Speaker: But very light on the business rules.

Michael Coté: Yeah, it’s like way back when, when I used to like do real work in program, like I think one of the best situations I ever got, it was like a really good DBA I was working with and he was like, just tell me the data structure you want. I was like, all this line of code. He made like some stored procedure and everything, it was great, because it was just like boom! He would give me like an XML thing, a document of stuff that I wanted. Now I didn’t have to worry about any of that.

So, then like the JavaScript you do it, it’s all sort of like around presentation, wrangling and things like that, like what — like what do you like pushing JavaScript to do beyond like rotate images and things like that? Like, that’s a pretty wide question, but like I mean, would you say that you’re JavaScript developers in the same way that you could be a Java Developer?

Male Speaker: Let’s say that the majority of the interesting parts of the application are in the JavaScript or a large portion of it.

Michael Coté: And are they sort of like business logicky things or UI things or –?

Male Speaker: We just push to the HTML or what’s around the way we want them.

Michael Coté: So, it’s all about manipulating the user interface to us, right?

Male Speaker: It’s a UI programming language for us.

Male Speaker: The funny thing is, I think the end users actually see the least of this, but the people who administer besides get to see the cool parts.

Michael Coté: Oh! So it’s sort of the admin tool where you see a lot more of the stuff then.

Male Speaker: Yes.

Michael Coté: Right. Well, those are close for the people who actually pay for the software. So, it’s always nice to make them happy.

Male Speaker: Yeah. Well, I mean, I guess we use JavaScript to maintain our own component library.

Michael Coté: Right.

Male Speaker: So we’ve got — we just have these little bits of display code that are little bundles of CSS and HTML and JavaScript that you can embed in one another, which is pretty standard, no matter what it is that we’re working with.

Michael Coté: So like, I mean, using my own wacky words here like what are like examples of like widgets or things you would make with JavaScript, CSS and HTML?

Male Speaker: Really, anything that you would want to reuse more than once.

Michael Coté: Right, right.

Male Speaker: For instance, we have a dialogue window component. So whenever we want to present stuff to the user like a model fashion. So we have one of those. We have a date-slider that lets us group sensible search results and then select them by date ranges as opposed — instead of having the type-in dates.

Michael Coté: Right, right.

Male Speaker: What else do we have? We have — our search result display is another JavaScript.

Michael Coté: I mean, are these things that you can’t like get — I mean, there is no shelf anymore, but you can get them off-the-shelf like you’ve got to build it on your own, I mean what’s your experience as far as — what’s your sense of like we need to build this from scratch versus we can go out and find something that does it.

Male Speaker: I’m always inclined to build it from scratch. I actually find something that does it, and then either use it and eventually re-implement it yourself or just do it from scratch. Find out how it works, and then do it from scratch, because you almost always end up being more lightweight and timely integrate with what you’re doing.

Male Speaker: I guess it’s also part of being a programmer, you want to have control and you want to do it yourself.

Michael Coté: Right.

Male Speaker: Yeah.

Male Speaker: Now just throwing stuff together to get it done.

Male Speaker: And part of the truth is pragmatic, right? I mean part of that is when if it doesn’t work, which is a lot of times, stuff [?] shelf. It kind of works or is close to working but you are running to an edge where it doesn’t, right? But if you implement it today, it will probably be a lot linear like Charles said and how it works.

Male Speaker: Probably be faster and also it’s going to look like you did it yourself.

Male Speaker: It wasn’t like you are trying to make someone else’s stuff look like your stuff.

Michael Coté: Right.

Male Speaker: You can tell when someone is using jQuery UI?

Michael Coté: So, how often?

Male Speaker: You can tell when someone is using ExtJS, you are like, oh! They did that with ExtJS.

Michael Coté: yeah, I just talked to those guys this morning.

Male Speaker: Yeah?

Michael Coté: Yeah.

Male Speaker: It’s really cool.

Michael Coté: It’s ExtJS, right?

Male Speaker: Yeah.

Michael Coté: Yeah, they had a pretty wide array of interesting customers.

Male Speaker: Yeah, you can build some really crazy cool stuff with that, but then it’s like, that definitely makes it look more like an application, because I think what, I think —

Michael Coté: More-and-more like an application than a website?

Male Speaker: Yeah, because when you talk about like rich Internet applications and stuff like that, you are bringing the analogy of the desktop to the web. But I actually like the kind of middle ground where a lot of the web lives, where you have got documents that are just weirdly interactive. It looks like a page but then all of a sudden this paragraph leaps out and starts dancing, if that’s what the situation demands. You know what I mean?

Michael Coté: Yeah. So, it seems like the point is, you guys want complete control over what the UI looks like and behaves like. And so if you are to use off-the-shelf stuff or just whatever, libraries are available, like you would be compromising the look-and-feel essentially?

Male Speaker: Sometimes, I mean, it depends on the components, right? There are some components that really lend themselves long, implement it well.

Male Speaker: And I don’t know why that is on the web, because I mean, if you would say that I am going to use my —

Michael Coté: You are going to write your own Charles Swing –

Male Speaker: Right, or Charles Coco or —

Male Speaker: You would never do that.

Male Speaker: Or heard Charles Foundation classes. Punch me!

Michael Coté: This is always a big debate we had like teams I was on is that, is the web isn’t constrained enough. So like people are trained with desktop applications, that there is only 30 things you can do, or whatever, and they all look this way. Like there is not any variation, and the counter-example of that is like, Winamp, right? If anyone remembers that.

Male Speaker: [?].

Michael Coté: Yeah, it’s just like —

Male Speaker: We make our buttons 4×4.

Michael Coté: Or more modern day thing might be, I don’t think anyone uses it anymore, but the OS X dashboard widgets, like those were like many applications and they are always sort of like murderous. But I mean, that’s sort of example of customizing things.

I mean, it seems like on the web, the expectation is the opposite that people don’t really like standardized interfaces on the web, despite — I mean, even when you go to like the big standards, all that’s out there, every site they make tends — well, first of all most standard people are not application people, they are document-oriented people and they are making very nice brochures on the website. But then also the way you look at is most of their stuff, it varies pretty widely between sites.

Male Speaker: Yeah, I mean think about it. I guess you think about it, you find the diversity of on the web of — interfaces of the web within the same level of diversity if you have in like objects you fined in the world, like this white-board, this table. Can you imagine if every object that we used was comprised out of 30 widgets? You have like buttons and drop-downs and stuff on my coffee mug.

Michael Coté: That’s like one of the things with Apple and the iPad that I am curious to see how it trickles out as far as the idea of like, not single uses and you only use it once, but like single type of use devices that are out there, right?

Like instead of having a laptop that does everything, you are cursed with like five different devices that specialize in each of the different things I do. I don’t know it would be an interesting different approach, it’s kind of like, I think I was ranting about this the other day, how I hate multifunction printers, those things drive me crazy.

Male Speaker: Oh yeah.

Male Speaker: Really?

Male Speaker: Well, I never — you always tell me some damn HP Printer I need to go.

Male Speaker: Have you bought it yet?

Male Speaker: But every single multifunctional printer has been terrible. I mean, just like it doesn’t really multifunction well.

Male Speaker: Mine has been awesome.

Michael Coté: So, this is the last question on this topic. It was, so like you said, you guys do a lot of your own JavaScript work and custom stuff, but what are like the libraries and stuff that you would use, like what are the things that you haven’t written that you guys rely on?

Male Speaker: jQuery?

Male Speaker: jQuery is the base.

Male Speaker: See, that’s really is just a, that’s DOM. It’s basically a better interface to your DOM. So, it’s not really a set of —

Michael Coté: So would you say you guys don’t write your own middleware, I mean, in the sense that there is middleware for the UI, right, and jQuery is kind of like a way of making, dealing with the DOM and all this.

Male Speaker: Right.

Male Speaker: Because that’s the point, yeah.

Michael Coté: I mean, would you say like you use middleware a lot or –?

Male Speaker: If you call jQuery middleware, then yeah.

Michael Coté: So what are other things that you guys source from others?

Male Speaker: In terms of JavaScript, I mean, right now we’re using that color chooser, it’s a hacked version.

Male Speaker: Almost we have in there. I mean, there is a bunch of stuff that we load, I’m trying to remember what we use it though.

Male Speaker: Well, we do that, we use the thing for color animation although that’s not necessary in jQuery 4. See there is that we use the Low Pro, but then we’re trying to get rid of that now.

Michael Coté: Yeah.

Male Speaker: A part of it is, if you use third-party components and you have a problem, you have to read all of the code, understand what it’s doing and that will fix the problem. If you go to yourself, you pretty much know what’s going on and you can fix it, no problem.

Michael Coté: Right, right.

Male Speaker: You raised a good point Mr. Coté, because if you look at things that way, you could draw analogy between jQuery and Rails. We don’t actually spend a whole, whole lot of time in Rails, right?

Michael Coté: Right.

Male Speaker: We spend a lot of time writing Gems or other Ruby libraries to talk to what we need to talk to. We just use Rails as kind of this way to manipulate the data we get from there.

Male Speaker: We use Rails basically in the URL Mapper.

Male Speaker: Pretty much.

Male Speaker: We probably did get away with Sinatra.

Male Speaker: We could have written – yeah absolutely.

Male Speaker: We could have written.

Michael Coté: When does Sinatra do?

Male Speaker: It is a really, really lightweight Ruby server.

Michael Coté: Yeah.

Male Speaker: It solves the problem of mapping URLs to content.

Male Speaker: It’s a micro —

Michael Coté: Kind of like a [?] for the Ruby.

Male Speaker: Yeah.

Male Speaker: Yeah, it’s a micro web framework.

Male Speaker: It’s a micro framework.

Michael Coté: Right, yeah. So when you look at all the technology and the stuff you guys code day-to-day, would you say it’s like — is it the same as it was like 12 or 24 months ago or is it like completely different? Like how often do you feel like you’re cycling two things? Like I feel like to do it I like doing over-contextualize, I feel like back in the Java.net days like you wouldn’t actually use new things very often. But it seems like nowadays, with some of my theory is, people are always – it’s like framework fragmentation, so you’re always using new stuff.

Male Speaker: You’re just using new stuff.

Male Speaker: Even when I was doing .NET like a couple months ago, we would still write our own stuff.

Michael Coté: Yeah.

Male Speaker: But for what.

Male Speaker: Control?

Male Speaker: But I mean what would you — like as opposed to using the stuff that you get from Microsoft or is this also like –?

Male Speaker: Maybe don’t, for UI things, yes, definitely, you want to go on your own, but you do get to use most of the .NET framework. You get that for free and you can build from there, but you don’t use components that are built with .NET in occupation.

Michael Coté: Right.

Male Speaker: I think that might be something very specific to both, Serial Solutions and Medialab to be honest, the companies that you two guys came from. The place that I was at before, that wasn’t the case.

Male Speaker: So you have a lot of off-the-shelf stuff.

Male Speaker: A lot of stuff that I came with whatever I was working on.

Michael Coté: So you are sort of extending existing —

Male Speaker: Yeah, absolutely.

Michael Coté: Building something from the ground up.

Male Speaker: Right, right. I think that a lot of my colleagues, a lot of people that I know, kind of end up in that same pattern. We’re talking about this little bit of dinner last night, talking about how the company that we’re at now at, Serial Solutions, they have a special way with developers, and they allow a certain level of freedom that’s actually pretty rare to find. They can have a lot of top-down architectural (Voice Overlap) like you will use these components for these types of things.

Male Speaker: Yeah, yeah.

Male Speaker: And I imagine you guys like that.

Male Speaker: Absolutely! Yeah. I mean, there is a lot of rope.

Michael Coté: Sure.

Male Speaker: And it’s easy to hang —

Michael Coté: Yeah, I know a lot of knots.

Male Speaker: Yeah.

Michael Coté: We carry a pocket-knife.

Male Speaker: That’s right.

Male Speaker: But that’s also a read and learning experience.

Male Speaker: That’s right.

Male Speaker: And you have to learn fast.

Michael Coté: So before we were recording, you were saying that you saw this pivot thing, which I have no idea what it is. But I think you’re saying is restoring your faith in humanity or something?

Male Speaker: No.

Male Speaker: It’s still at all times.

Male Speaker: It’s literally the first thing in 15 years that Microsoft has produced that have been like, wow, I might actually consider getting an instance of Windows running.

Michael Coté: So what is it, tell me what this pivot deal is?

Male Speaker: Well, I don’t know if I’m ready to give a demo.

Michael Coté: You don’t have to give a demo, it’s only audio here. So just tell me what’s going on with this pivot?

Male Speaker: I’m imagining the gathering. Basically it’s a way to visualize data.

Michael Coté: Oh, yeah, I’ve seen this thing. Is this part of the Seadragon stuff? I haven’t like — I’ve actually —

Male Speaker: I think it’s based on their technology.

Male Speaker: Yeah.

Michael Coté: I’ve actually like red — I do — I track a lot of like big data and analytic stuff and I haven’t’ gotten around to checking out pivot in depth, but now that I’m seeing it, I’m remembering that I have.

Male Speaker: That’s pretty cool!

Michael Coté: Oh, yes. So basically what it is, is Seadragon is — I forget what they — it’s called Deep Zoom nowadays.

Male Speaker: Yeah. That’s the Photosynth part of it.

Michael Coté: Yeah, and it’s a way of like — I mean, sort of canonical Deep Zoom, Seadragon, whatever example is, like what we just saw where you’ve got all these little Magic: The Gathering Cards and you have the super zoomed out view, you might be seeing thousands of them and you can like keep zooming in at higher-and-higher quality on each thing.

Male Speaker: But the cool thing about pivot is, it lets you zoom out again as well. So when you drill down to an item and you go — you get the properties and you can select one of the properties.

Michael Coté: So true to its name it lets you filter or pivot on various attributes of the data that you’re seeing. So, like these cards like you just selected at green so now you can see the collection of all green cards. And I guess you could also see all cards involving goblins or something and stuff like that.

Male Speaker: Yeah, all these on the side are basically your facets.

Male Speaker: Right, that’s what they call them.

Michael Coté: There is always all this fancy vocabulary of things, always love the facets. And so this, you are like, oh, and this is — they do this on Silverlight, I guess.

Male Speaker: Yeah.

Michael Coté: And so you’re thinking like now I need to get some Silverlight?

Male Speaker: Well, no I was just like, wow, that’s compelling.

Michael Coté: And then you were telling me about this and right afterwards, I think you said HTML5 can do that, which is kind of funny.

Male Speaker: You even have to implement it.

Male Speaker: You have to roll up your sleeves, yeah.

Michael Coté: I mean, you guys are pretty big HTML5 believers, right, would you say?

Male Speaker: Believers?

Michael Coté: You all for it?

Male Speaker: Yeah.

Male Speaker: We can’t wait to move to it.

Michael Coté: Yeah, yeah, definitely.

Male Speaker: It’d be nice. It’d be nice.

Michael Coté: So, while we are on top, like Silverlight here, so we were kind of talking the other day how you have been using early editions of Visual Studio 2010, which is the big combo. So, what do you think? What were using it for?

Male Speaker: .NET development, ASP.NET.

Michael Coté: Yeah, yeah.

Male Speaker: I have to say, I was coming from 2008, I was pretty impressed. It feels snappier. The interface is nicer. They’ve built in a bunch of re-factoring tools that you have to use slow external tools before.

Michael Coté: What were the external tools you used to use?

Male Speaker: ReSharper mainly.

Michael Coté: Okay.

Male Speaker: I probably used only 10% of it, but the 10% that I used, I could not live without like looking up symbols, files, just not having to use the mouse and just being able to keep in the flow. I think they pretty much nailed it this time.

Michael Coté: Yeah, yeah. And are there good ASP.NET improvements or like what’s going on in that area?

Male Speaker: I honestly could not tell you because we were still using ASP.NET 2.0 for our stuff. So I haven’t been able to really dive into that. Although, I have been dabbling with Windows 7 trying to use some of their new UI components and they look a lot better than those stuff, like more like the Apple Cocoa.

Michael Coté: So, when you’re looking at those new components, like what are you — and taking from like — what are some things you’re kind of imagining would be good things to put in applications that Windows 7 gives you as far those components? Like what are things you’d like to take advantage of, if you could?

Male Speaker: Yeah, in the Toolbar, when you right-click an icon, you get a whole list and you can pin it to the – you’ve got all these talks in there, I think that’s really neat.

Michael Coté: It’s sort of like — I forgot what they call it, but it is like the contextualized task or something like that. And you can extend that, right?

Male Speaker: Yeah.

Michael Coté: So, instead of relying on like — it is always that hokey thing, as tend to services or something. It always seems like a place where there is a lot potential, but never really gets taking advantage of, because — I think it’s because you have to know AppleScript, which seems terrible. But it looks like if you’re probing something in Windows 7, when you get to this task list, you can basically build workflows in from the menu there, which is kind of interesting.

Male Speaker: Or even like recently used stuff for LAN application, not being — not having to drill down in the menus and just having it available from the toolbar.

Michael Coté: Right, right.

Male Speaker: It just makes working with it too much faster.

Michael Coté: Yeah, yeah, that is interesting.

Male Speaker: You have to think less about how you’re going to do it and you just do it. I think that’s a big improvement in Windows 7 and APIs, you’re building into that.

Michael Coté: Yeah. So do you do a lot of stuff in Visual Studios nowadays or it’s just in the past?

Male Speaker: Nothing nowadays.

Michael Coté: Yeah, did you like doing like Microsoft world development, what was that like?

Male Speaker: Now I’m back in the Ruby world, I have to say Ruby, I miss it. It’s not as dynamic and once you get used to that, it’s hard to go back.

Michael Coté: Yeah, so it’s not necessarily that tools or whatever, it’s sort of the characteristic of the language, like you like dealing with Ruby as a language versus the ASP.NET stuff or C# or the more statically type things.

Male Speaker: The thing I do like are the Compile-Time Warnings, the early catching of problems. But the amount of profits you get for having — just for having that, it’s not worth in my opinion.

Michael Coté: Yeah, yeah, well, that’s great! Did you guys have anything else you want to do or pile on?

Male Speaker: [?].

Michael Coté: As happened.

Male Speaker: As happened.

Michael Coté: Alright! Well, thanks everyone for joining me in the inaugural Make All edition podcast episode, whizbang here.

Total Duration: 26 Minutes.

makeall001

Transcribed by Tech-Synergy Page 1 of 16

End Note

While doing RIA Weekly I’ve been passing on some great chances to cover more general software development topics. Also, I’ve been falling behind on keeping RIA Weekly, well, weekly. Last week, I decided to kill two birds with one stone and start a new podcast. I’m calling it make all and if you think that’s even remotely funny, it’s probably a good podcast for you. Be sure to subscribe to the podcast feed to catch all the new episodes! As the name implies, I want it to be about all sorts of programming, coding, and the more nerdy side of software.

I’ll still be doing RIA Weekly for sure – I’m just going to fold it up into this new podcast – a sub-show if you like. Hopefully this will mean more, regular content instead of the blockage I currently have. In truth, RIA Weekly has been trying to expand beyond its RIA beginnings for awhile and the more recent episode show that in an exciting way.

If you’ve got some development topics you’d be interested in seeing, pass ’em along. I’m looking to make this more of a variety show (lots of little segments) than my usual gonzo, long-form style – so I’ll be on the hunt for lots of little conversations in addition to the longer ones as in this first episode.

Disclosure: Microsoft is a client – see the RedMonk client list for other clients mentioned.