For some people, RSS (Really Simple Syndication) is a way of life. For others, it’s just another acronym that they kind of/mostly/pretty much understand. In part 4 of our screencast series on Nuts About Southwest 2.0, Eric discusses RSS basics using examples from the various feeds on the Nuts About Southwest site.
And don’t worry, I’ll be back around next time. Enjoy!
Nuts About Southwest part 4 - RSS Feeds
Other screencasts in this series:
They don’t make them like this anymore!
RD2 is actively seeking a web application developer. Come join our team!
We have a focus and passion for building beautiful applications that help our clients connect with their communities. Right now, we have a place for someone who can work with an awesome team and who can inspire us with their talents. Please apply if you:
Adding to our team is no small task. Our environment is paramount to our success, and finding the right fit is something we know will not come fast. We’re committed to building upon our momentum, but know this is more of a marathon than a sprint. We’re looking for Web Application Developers who share our focus on creating great user experiences. We hope to provide a home for someone who is not afraid to share their experience in a team atmosphere.
High Level Experience:
A thorough understanding and experience with web technologies such as HTML/CSS, JavaScript and PHP/MySQL are obviously required. We also have positions available for someone with a thorough understanding of Microsoft’s .Net and SharePoint.
Additional and Important Details:
If interested, please forward your resumes to jobs@rd2inc.com.
We look forward to hearing from you!
“Help me Obi Wan Kenobi, you’re my only hope.”
We’ve been having some internal discussions lately based on a (seemingly) simple sentence in some of our internal documents: “RD2 is an acronym for our methodology: Research, Design, Develop.” This got us talking about our name.
While “Research, Design, Develop” simplifies the process and is not entirely unrepresentative of our Approach, you may have noticed on our Community page that there is no one whose job title sounds like “Research.” You may have also noticed the sentence that says “We are a small community of strategists, designers, technologists, and managers.” Where do all these departments fit in?
In response to some discussions on what our name really means and how it defines us, Chris sent out the following email. Enjoy:
When coming up with our name, I had a list that I was keeping which had over 250 possibilities. It was aggravating as hell because just when I would come up with something that I liked, the domain would be taken or there would be potential trademark issues. I’ve been lucky to have good guidance on some of the things that people don’t often think of when inventing a name for their new company. I retained an attorney to do trademark searches etc. for names that could be construed as legal conflicts down the road. So, the challenge was this:
… This eliminates so many damn possibilities.
David Slack then came up with a sample identity that I liked, but he was trying to sell me on something with my name in it, which I hated. But some of the words that we used in the branding exercise had to do with simple, minimal, effective — boiling the methodology down to: research, design, develop
The Dallas Company, Not the Robot: So, RD2 was born. I like the movie Star Wars, but don’t take it the wrong way… It’s not like I have a hidden stash of Star Wars action figures that I play with in the bath tub…
At first I was not very into the name because of the close sound of “R2-D2.” But after really, really thinking about it, my conclusion was that it’s not so bad having a familiar sound of the famous little droid. It’s not as if this is a negative brand image. In fact, R2-D2 is on the side of Good… fighting the opposing forces of the dark side. R2-D2 has a mind of it’s own… it’s willing to explore. R2-D2 traveled with Luke Skywalker to the Dagobah System, where he met with Yoda. Without “R2″, Luke may never have become the great Jedi Knight. R2D2 is a messenger, a confident little droid with a quirky personality yet has the intelligence from many distant galaxies. R2 wanders without hesitation through a fire fight with storm troopers and confronts the root of all intergalactic evil…a long time ago, in a galaxy far, far away. R2 periodically gets in trouble, falls down, gets back up, and lives to see another fight. R2 is a survivor!
So, we knew that RD2 was going to forever be the subject of an association with this famous little droid. And how bad is that? We’re not KFC, having to move around our name and long standing brand to hide what was once an appropriate image, prior to the American Heart Association’s campaign against fried food, trans fats, and so on.
The little wise cracks are actually not only harmless, they are a compliment. The way I see it, we have nothing to worry about unless George Lucas releases a sequel to Return of the Jedi, with a twist… Where R2-D2 was, all along, a secret spy for the Emperor, and was an instrument of terror and intergalactic mayhem, then I think we will find ourselves in the same brand quandary as KFC. Until then, I’ll gladly accept the “accidental” association.
The point of all this is that the brand is far less about the name. It’s a beacon for the story. It’s a symbol that becomes associated with a mantra, a community, an emotion, and if we’re lucky…an inspiration. At first, we shifted the meaning of RD2 to Research, Design, Develop. It was appropriate for the time and conditions for our business. It was short for our Methodology. And what do we know about Methodologies? They are [edited]s… everyone has one. Methodologies are becoming like mission statements. You always have one, but no one really wears them like a prominent tattoo any longer. A good friend of mine, Sally Herbert, is the best consultant I have ever worked with. She never used the word “Methodology”. As sophisticated as she is, she never used those big MBA words. She always went right to the “Approach.” So, when you hear me say it, that’s a phrase that came from her. The word “Approach” to me seems more as if you are prepared for action. You have your tools, instruments, landing gear, and all of your focus aligned and ready for what’s ahead.
The name of a brand is in the story, and over time becomes an emotional connection within those who are part of it and within the community that surrounds it. A mission statement and methodology are more like the English aristocracy. It’s just an ornament on the tree. It’s there, but really has little to do with the day to day goings on.
So, who is RD2? We’re a determined little company who knows how to build online communities, engaging an audience with our clients. We have a history, a methodology, and all that mission statement stuff… But most importantly we have a specific Approach which we have used successfully to systematically solve complex problems. If we get to know you along the way, maybe we’ll have a few cold ones and talk about droids, battle scars, and the thrill associated with the lifecycle of a company that simply never quits until it finds it’s way…
Oh, by the way… RD2, Inc. and it’s logo are a registered trademark!
- Chris
Last night I decided to continue my Steak Quest to find the best steakhouse in DFW.
So, here’s an update:
By taking an informal poll of everyone at our office and random, unsuspecting people on the street, here’s the entire list of steakhouses that’ll be subjected to my taste testing:
I’ll try to visit them in that order, but that may change depending on the day, my mood, my credit score, or whatever. With that said, on with the reviews:
Yesterday took me to MIGNON in Plano, TX. They’re known for their seafood dishes and I just had to visit them after a friend insisted that it was undoubtedly one of the best, if not the best, steakhouses in DFW. I hope he’s right or somebody owes me gas money.
Instead of going alone, I brought along my best friend with promises of steak nirvana and other such false hopes. Plus, it’s always a blast to dress up and go to dinner with a close male friend and have most people assume you’re on a date. It’s this kind of social derangement that I live for.
We arrived around 8:00pm. The exterior of the restaurant resembled an old shoppe in France, complete with curvy typefaces, subtle paint, and molding.
We enter and are greeted quickly. Walking to our table, we pass the bar on our right. It’s adorned with glass, some nice textures, and has the typical liquor-bottles-as-trophies display. Do people really care how many types of tequila are on hand? I’ve always wondered this.
The rest of the restaurant is decorated in similar textures, and a combination of yellow, red, and brown color variations. We notice that some of the walls and columns are finished with a cool-colored, mosaic tile pattern, and we even notice a booth that has walls that resemble some sort of funky strawberry swirl. It’s an odd combination of features, but they all fit together very nicely. It’s classy without being tacky, and it’s all very, very French. Even the servers had accents.
We sit down and get right to business and order a couple of appetizers. First up, a plate of Bruschetta followed by Braised Beef Short Rib.
The Bruschetta was good, but nothing spectacular. It had a good paste (or spread), but the flavor was too subtle for me, and the red, green, and yellow cherry tomatoes that were supposed to compliment the dish seemed to overpower it. It’s a decent start, but there’s always hope, and we’re not exactly here to judge tomatoes. The Braised Beef Short Rib, which I actually ordered on an impulse, was an entirely different story. This appetizer was definitely not screwin’ around — the first bite was somewhat intoxicating. The beef was succulent, perfectly seasoned, and you could cut it with a fork. It sat atop a bed of garlic mash, also perfectly seasoned, with only a hint of gravy. The beef seemed to melt in my mouth and I just savored it like fine wine.
For the main course I ordered the Prime Grilled New York Steak (14oz). I would’ve gone with a top sirloin but Mignon doesn’t serve that cut of steak.
My steak arrives after a short wait. Just as in the Bruschetta and Short Rib, the dish was arranged and presented very nicely. It was like a dining scene right out of American Psycho’s Dorsia. It sat on a bed of Roasted Fingerling Potatoes and Green-Pepper Corn Brandy Sauce. The potatoes were nicely roasted, but the real kick came from the brandy sauce. I’m starting to see that it’s not uncommon to have the condiments on a dish be the star of the show, and this was no exception. I cut into the steak, and it’s cooked medium rare as I requested, a beautiful palette of red hues. At 14oz, it’s the biggest steak I’ve ever had. The outside is a nice dark brown, and the steak is thick enough that I can cut it into tall slices like one of those big-ass Thanksgiving hams. I take a bite and the Matrix tells me it’s juicy and delicious. Every time I put a slice in my mouth, I let it sit on my tongue while I absorb all the juices. It’s good, really good. With every bite it seems like the flavor of the steak matures, and it just keeps getting better and better. Once I’m halfway through, my stomach is full, but I continue eating anyway because wasting such a savory slab of meat is a social crime.
Overall, Mignon does a great job of creating a unique environment. That type of experience is something I rarely encounter in restaurants anymore. It’s not just about the good food and the ritzy wines, it’s about the French surroundings, the service, and the presentation. For two people with appetizers, a main course, and some liquor, it cost us about $140. It’s definitely pricey, but it’s definitely worth it. It’s time to forget your lame, usual Friday night eatery and put on some cufflinks and take your ass to Mignon!
We’ve added a lot of functionality to Nuts About Southwest (Airlines), and we’re filming this screencast series to be sure that none of the cool new features get lost in the excitement of a new site. The following screencast is “a behind the scenes look” at the flickr images you see on the Nuts About Southwest site. It presents a basic step by step look at how to post images on flickr and to the Southwest Airlines group.
Presenting, part 3: Nuts About Southwest part 3 - The Southwest flickr Feed
If this is basic knowledge to you, you are among the few flickr users who know how to join a group (many don’t). If this screencast shows you something you didn’t know before, you’re definitely not alone.
Other screencasts in this series:
Last week, my brother and I had a discussion on who has the best steakhouse in the Dallas area. He insists it’s Three Forks restaurant, another colleague of mine claims the title belongs to Mignon in Plano, and personally I’m undecided.
So, this week I’m on a quest to find the Best Steakhouse in the Dallas area. The prize? Absolutely nothing, except maybe some dignity and a little publicity on our primo blog.
The criteria? I’ll rate everything from the atmosphere, to the service, and obviously the food. But mostly the food. There’s no scoring system or any of that nonsense. I’ll just pick a winner at the end, whenever that may be.
Today I visited Y.O. Ranch Steakhouse, across the street from RD2. Their exterior signage is ostentatious and can be seen from space, and we walk by it nearly every day when we’re heading down to restaurant central. I decided they’d be the first restaurant in my test of trials.
I was seated promptly (I told the server I was on “a quest” and she seemed okay with me being insane), the restaurant was clean and only moderately noisy — mostly full of business men and women. We’re off to a good start. Speed of service is critical.
The first thing I ordered was a chips and salsa appetizer. Why? Because a restaurant’s food quality can easily be measured by judging how they prepare simple dishes like chips, bread, soups, and so on. If they can’t bake bread properly, then how the hell are they going to prepare a steak? You get the point.
The appetizer was great. The chips weren’t heavy or greasy, and the salsa had a sweet, tangy flavor and was only mildly spicy. Overall, I think this steakhouse serves up a better combo of chips and dip than most Mexican restaurants I’ve been to.
The next item up was a simple salad with the house dressing. The salad itself was obviously pre-made. Nothing special — just some spinach and greens surrounded by sliced tomatoes. Despite that, the dressing was perfect. It was a cilantro vinaigrette that tasted like no other dressing I’ve had before. It was also tangy, and slightly spicy.
My main course was an 8oz. top sirloin steak. I chose the top sirloin because it’s my favorite cut of steak and it’s what I commonly order at a steakhouse, so it’s easy for me to compare.
The steak was cooked just I had requested — medium rare, and cooked evenly on all sides. It was super-juicy, easy to cut, smelled great, and tasted even better than it looked. The steak was presented next to a side of mashed potatoes that had a hint of barbecue flavor (not my thing), and a bed of vegetables that included zucchini, broccoli, cauliflower, and peppers. With the exception of the mash, everything was seasoned perfectly. I prefer less gravy with my food, so that’s the only change I would’ve made to the dish.
Lastly, I had some banana pudding, compliments of the house. This was an unexpected surprise, and although I’m not a fan of pudding, the banana dessert tasted pretty good. It was warm and a little wafer adorned the top (I love wafers). I had only a few bites but only because I was so full from the steak.
Overall, it was a good experience. The total tab was about $20 (the steak was $15). If you’re ever downtown, stop by Y.O. Ranch Steakhouse.
It’s a slippery slope, with potholes, rusty nails, and a sundry of other snags ready to pull you into CMS bliss or hell. Truth is, there’s no perfect match. Even when strategically aligning your team and goals within a framework for decision making, there’s somewhat of an art to the selection of what fits and what does not.
Having recently launched a couple of new community websites, I find myself reflecting on the pains of the past when watching and assisting people we work with as they begin deploying their content. Jeremiah wrote this timely post making a call out for the peeps in his community to share horror stories as well as share their ideas for future-proofing their CMS systems. So, while I had CMS on the brain, Jeremiah’s post inspired me to go with this one…
Generally (very generally) there are two big camps you might find yourself in when evaluating your approach to a Content Management System for your organization. We could split this beyond just two camps, but I think we generally do a pretty bad job in our industry of simplifying things, so I’m trying to simplify. The two camps I am referring to are:
This consideration is where the first big mistakes are made. I find myself in a lot of discussions where the words “Open” and “Source” conjure up a few preconceived notions. Let’s address some of those with respect to the first one of our camps:
Open Source is not limited to the Linux, Apache, MySQL, PHP stuff that we keep hearing about. There are plenty of open source applications out there that are even of the Microsoft variety. That’s right, I just used the “M” word. There are many who are already squarely locked into a Microsoft infrastructure and there’s no getting around using something that will integrate well with their existing enterprise systems. And, that’s perfectly fine. There are solutions available such as DotNetNuke, Rainbow and Umbraco.
If you’re in the Open Source camp, Microsoft technology lies beneath a number of options that might fit within your technology stack. If your search moves you away from the Microsoft technology set (for reasons such as cost, integration or consistency with your enterprise road map), you may be in the confusing space where the lines blur between countless Web 2.0 applications. Danger ahead! Some of these applications can, and very well may be, like heroin — One of the great things about all of the applications you may find yourself looking at is how these low cost, easy to build, sexy looking applications satisfied some immediate needs, and even helped build amazing communities to boot. In many ways, these applications helped to build working business cases for companies to think in a more sophisticated way in how they engage their communities. So, what’s the problem with all of these shiny, bright colored applications? Nothing at all — They have helped to democratize (oh my gawd, I can’t believe I just used the most overused phrase on the web) the way we think about the web… about igniting communities and stimulating many millions of conversations. While so many of these applications satisfy the urge to be more socially compliant, they are fundamentally split from the business models of many online commerce models. In the plain-est possible speak, these are the applications that excited and inspired us about the power of going social… they validated the concept and value of community… and now corporate officers are taking it seriously — really seriously. What does that mean? We now have challenges on our hands of integrating these applications into the enterprise. We’re going from a bunch of successful experiments to a market who takes this seriously and now wants it to fit inside their enterprise.
So — When picking a winner, some of the old methods still apply. Evaluating your solution and applying just any Web 2.0 approach is a “top down” way of thinking. Don’t get me wrong, I love the bling, bling social stuff… but it’s generally “bottom up” thinking that goes the long haul.
In the past, we have referred to Drupal VS WordPress. Reason for the comparison, is that WordPress is arguably a killer solution for a specific thing. If you want to build a great blog and have the ability to add bling, then it’s awesome. You can even use it for light weight content management. But, the mindset of WordPress is all about blogging — social — community. Drupal comes from a Content Management mindset. Even the tone and content created by the community is different in tone and approach than your typical community building solution. It’s got more of a content management flavor to it. Within the last few releases, Drupal has asserted itself as a CMS solution with an appetite to add community everywhere.
Drupal VS WordPress is a good comparison to make a simple point…although it’s shallow in the bigger picture of what’s really available and completely bypasses the important part of picking a winner — the process of picking.
If your enterprise is not ready to go enterprise yet, then you’ve got to be careful and not shortcut the process. Here are a few things to remember as you stand on the edge of what could be a very important decision. Even if you don’t plan to be at your organization after another year or two, someone will need to pick up where you left off. Here are some things to consider:
Going forward, we’ll try to share more about what we are finding. We’ll try extra hard to use plain speak (please let us know if we are being bone heads and pushing the tech talk). The big take-away is however, that jumping into what looks like shallow water can result in jumping right off the continental shelf. The most successful implementations we have seen always occur when the right planning is put in place. It’s never time ill spent.
It’s the same Nuts About Southwest, but of a slightly different variety. Some like their peanuts dry roasted, some like them salty. Even if honey-roasted is your flavor of choice, there’s something for you at BlogSouthwest.com.
The blog for Southwest Airlines just turned two, and we are celebrating by bringing the conversation to a wider audience. We know that people engage websites in different ways. While I might prefer to spend my time reading Brian Lusk’s blog posts, others may prefer to listen to Steve Heaser’s radio voice on RedBellyRadio. Then, if you are into watching video, Christi Day shares her enthusiasm on the Video Blog. Of course, there are many who like it all mashed together, providing everything in one place.
We hope you enjoy the new BlogSouthwest.com. We have had such a great time working on this and have had a rare experience to do exactly what we LUV to do. Gotta hand it to the Southwest team. They have the content part of this whole thing figured out.
We’ll be posting more later on this as we want to help Southwest share the features and functions. Our team is preparing presentations for our blog where you will get to meet them and hear about their contributions.
Many thanks also to Paula (did you think I would forget you?). Not least, Paula Berg (AKA BlogGirl) is a rock star who does everything at 100 mph… without sleep!
UPDATE:
Here’s an introductory screencast, the first in a series we’ll do on the new site. Thanks Caitlin and Eric for the narration!
Nuts About Southwest 2.0 - Introductory Screencast
UPDATE #2:
Screencast part two - logging in to the new Nuts About Southwest. Enjoy!
SWA screencast part 2 - logging in
There’s (still) lots more to come!
