Engaging with IT Professionals via Twitter

Listening to the Geek Whisperers and pondering their viewpoints on how to effectively engage with IT folks through social media got me thinking about my own experiences with this. Participating in social networks (especially Twitter) and generating content like blogs and podcasts are the ways we get to know each other, exchange ideas and information, and set the stage for the occasional meatspace run-in at a conference.

For the most part, social media is a nice way to develop a sense of community. Social media is also a colossal distraction and occasional frustration, but on the whole, it’s useful. From a career standpoint, I can make the case that engaging effectively with your peers via social media is a boost.

If you don’t get the whole Twitter thing, that’s fair enough, and the best thing I can suggest is to build an account and follow technical people you might know from reading their blogs. Then find out who they interact with and follow them, too. Eventually, you’ll be keeping up with the conversation and getting a sense of it. From there, you should be able to jump on in and start participating within the proper context.

Some other thoughts on how to make the most of the Twitter experience.

  1. Don’t be a tool. If you’re about to hammer on someone for their opinion, it’s possible you don’t understand it. Even if you do, then there’s still nothing wrong with a mature, reserved discourse. Twitter’s a terrible venue for that sort of discourse, though. 140 characters minus all the handles you’re tweeting to means your message is likely to be too terse or cryptic for your no doubt nuanced and well-informed viewpoint to be clearly articulated. It’s hard to have an adult conversation via Twitter; a twitpiss rarely ends well for anyone.
  2. Don’t be ignorant. If you’re going to say something, understand completely what you’re talking about. If you’re not sure of the details, pose your tweet as a polite question instead of a firm statement. That way, you’re gathering information instead of demonstrating that you don’t know what you’re talking about. There’s nothing wrong with not knowing. There’s a lot wrong with not knowing, but acting as if you do. Or worse…thinking you do, when in fact you’re wrong.
  3. Don’t be a vendor shill. If you work for a vendor, you’ve got to be balanced in your comments. Most of the vendor employees in my Twitter lists are very good at this. They don’t beat up on competitors. They don’t sound like a non-stop ad for their employer. They engage with others in the Twitterverse about technology, but sometimes other things, like bacon. A profitable and enjoyable experience is had by all. Some other vendor employees elicit an inward groan everytime they pop up, because I know I’m about to hear a commercial or other comment colored by the mother ship. I want to read thoughts shared by a human with brain, not a soulless marketer spewing out recommended tweets.
  4. Don’t be a fanboy. Worse than the vendor shill is the vendor fan boy (whether employed by the vendor or not) who bashes other companies at every opportunity, usually uninvited. I’m glad you have a favorite vendor, but if you really think they are *that* superior to every one else in the marketplace, you haven’t been playing the IT game long enough. IT practitioners are the brokenhearted, the disappointed, the cynical and the jaundiced. You *will* experience problems in your data center because your favorite vendor has failed you…if not yet, then soon. Probably very soon.
  5. Don’t be a vendor shill fanboy. (See what I did there?) This whole post was inspired by a Very Special Vendor Tweeter & Blog Commenter who says things are are, at various times, abrasive, ignorant or an overt attack on competitor’s products. If you’re going to be obnoxious, at least have the benefit of a well-formed point of view on your side. Otherwise, no one cares what you have to say about two tweets and/or blog comments in. You’re just embarrassing yourself and your employer, who’s probably going to be cranky when they grok what you’re on about. I can tolerate a certain amount of hyperbole & drama when you know what you’re talking about. I can’t when you don’t.
  6. Do…engage. Listen. Be witty. Create. Think. Share. Offer. Question. Apologize. Help. Thank. Research. Acknowledge. Collaborate.

The point of the “do” section is that social media isn’t about followers or about *you*. It’s about the larger community. When you come at it from that perspective, my take is that it works better.

But please, follow me @ecbanks. Please oh please oh please oh please oh… ;-)

CCDE Group Study Mailing List Formed – Sign Up via URL If You Like

I built a Google Groups mailing list for people interested in CCDE. Yes, there’s a Cisco Learning Network CCDE community, but it’s lightly traveled. Plus, you’re forced to use the web interface from what I can tell. (Someone let me know if I’m wrong about that – maybe I didn’t click/mash my way through enough icons to find the right settings.) Since I’d much rather have a mail-only option, here we go.

https://groups.google.com/forum/?fromgroups#!forum/ccdegroupstudy

As of this morning and to the best of my knowledge, I’ve invited everyone to the list who expressed an interest via e-mail, Twitter, blog comments, or LinkedIn. Going forward, CCDE candidates can sign up for the list at will using the URL above.

The group is global with a variety of networking backgrounds – looking forward to a good information exchange.

CCDE Study Group – Updates

Three quick items for those interested in the CCDE program.

  1. I’ve created a Google Groups mailing list for CCDE group study, and I’ll be sending out invitations shortly to everyone that responded to my query. The idea is to use the mailing list to coordinate study activities, exchange information, and engage in technical discussion. I believe there is at least one CCDE study mailing list already in existence. I don’t mean to step on anyone’s toes if that’s how creating a new list is perceived. It’s more that I’m trying to get together a specific group of folks that responded to my inquiry about putting a study group together.
  2. I’m talking with Cisco about the possibility of a CCDE wiki that would help organize the knowledge domains and provide candidates with a better plan of attack for the program. I’m a big believer in organization when going after certifications. Right now, the CCDE plan of attack seems to be “read a lot of books,”  ”take the tests,” and “good luck.” Cisco might not want a wiki outside of a domain they own (like the Cisco Learning Network), so I don’t really know how this is going to work out yet. I do have support for the wiki idea from one person closely associated with the CCDE program; they agree with me that such a tool would be valuable to candidates, and that it doesn’t already exist. I’d like to build this wiki outside of the CLN to be honest, because I don’t care for the busy and “social” CLN look and feel. CLN needs a lot of clicks to find anything, and the column format they use is too narrow for my tastes. (Which isn’t to say CLN isn’t popular…because it clearly is.)
  3. I’ve gotten a good head of steam up reading “Optimal Routing Design, and plan to start blogging through the big ideas as a way to keep important concepts in my brain. This approach seemed useful back when I was doing this same thing in 2007-2008 for CCIE prep, so I’ll try it again. Now, *if* the wiki idea comes together, I would most likely turn from blogging to writing wiki entries instead. TBD.

An Introvert’s Brush with Las Vegas

Until 2 days ago, Las Vegas had always been a remote curiosity to me. I’ve seen the tourism ads on TV that tend to be a little racy and generally inappropriate. “What happens in Las Vegas stays in Las Vegas” has become a boring, overused meme where “Las Vegas” is swapped out with anything apropos (especially if it isn’t). The “Sin City” moniker implies Las Vegas to be a place of wanton hedonism, where one can act out their naughtier urges without inhibition. And then there’s the shows. And the buffets. And the gambling. On it goes.

In short, Las Vegas is not my kind of place. When I need some downtime, I like to drive in my car…by myself. I like to hike in the woods…by myself. And just in general, I like quiet. Serenity. Springtime in my New Hampshire home office is glorious, as I can sit with the windows open and listen the songbirds accompany a Beethoven piano sonata while I do network design, research and write. That’s living.

With trepidation then did I step off of a plane and into the Las Vegas airport. It was as if a purpose-built assault team had assembled to create a place that would make an introvert wilt on contact. An army of slot machines, bright lights, and advertising placards greeted me, with half the place covered by screens, lights, or signs. And there’s noise. Noise, noise, noise. Such an unholy racket of machines clanking and computers blarting and recorded voices inviting you to do this or that.

Las Vegas airport welcomes you with a slap in the face. BOOM!

This is three steps inside the airport, mind you. It gets worse.

After weeding through the sea of signage to find the ones that told me how to get out of the airport, a cab ferried me to “the Strip.” The quick drive from the airport to the strip was yet another assault on the senses. The cab itself had a screen inside spewing forth a virulent diarrhea of advertisements. The approach to the strip was exposure to some of the largest ads in the world, where lighted billboards taking up the entire sides of buildings would beckon viewers to come see a show. After roughly ten minutes of travel, I was dumped at a resort/hotel/casino property, and walked inside.

Oh. Oh, my.

Mandalay Bay is a mall, casino, hotel, and collection of restaurants all in one massive complex of stone, glass and electricity. And where the Interop convention I was attending was held. Because, oh yes, Mandalay Bay is also a full conference venue that could house the reported 13,000 attendees, no problem. This was not a merely complex of buildings – I never went outside once I went in – as much as a city all its own, with every service & luxury you can imagine available to those who can pay.

This shot below is from an area near the MB lobby. Not whatever the official casino area might have been. Not deep within the bowels of the massive complex. Just inside the door. This was taken very early in the morning as I was on my way out to the airport, thus the dearth of people. But still. Just look at it. All the lights and sounds. And that carpet! Ugh. Everything is just so busy and over the top.

Mandalay Bay - near lobby

Mandalay Bay will kindly thank you to leave all of your money in these convenient collection devices.

Las Vegas is everything I’m not into. (I might have to make an exception for the reported buffets, which alas I was not able to explore during my brief trip.) I wouldn’t go out of my way to go there again, certainly not for vacation.

Now I’ve a question for you well-traveled readers. In the context of how Las Vegas felt to me and assuming my spouse aligns with me on the introvert scale, would we like…

  • An Alaskan cruise? We’ve discussed perhaps visiting Alaska at some point, and a cruise seems like an interesting way to do it. Or is a cruise ship just Las Vegas in the water?
  • An all-inclusive resort in the Caribbean? This is another idea we’ve had. Or are these places just Las Vegas on the beach?

CCDE – Study Group, Anyone?

After being cajoled by Russ White and others to go after the Cisco Certified Design Expert (CCDE) certification, I’m going down that road. There’s many reasons for this.

  1. Finding success in the CCIE program back in 2008 convinced me that nothing is out of reach, assuming proper study and self-discipline.
  2. The CCDE is not Cisco-specific in the way that many other Cisco certifications can be. The program purports to teach vendor agnostic network design principles. This is what I want.
  3. I am more interested in design and architecture than I am in implementation and operations at this point. I’ve been doing both for a long time. While I don’t want to walk away from the equipment, I do want to get my brain opened up to new approaches building networks. I’ve become myopic, and it bothers me a lot. I want my ingrained patterns to be challenged.
  4. I have just under 12 months to recertify my CCIE. This is my third recertification cycle. The last two, I’ve done at the last minute by recertifying with the CCIE routing and switching 350-001 exam. The CCDE written also recertifies a CCIE, so I’ve got lots of incentive to at least get the 352-001 CCDE written exam passed.
  5. I’m getting to a point in my personal life where I can see more freedom to travel and consult coming. Right now, I am Dad to two kids, and so I’ve been loathe to travel or consider consulting engagements. Instead, I’ve stuck to day jobs where I can be home more or less predictably. While my kids will still be at home for a few more years, they are getting old enough now where I can start thinking about what’s next for my career. Being a CCDE titleholder along with CCIE will, I believe, open up interesting opportunities to participate in projects I might not have been considered for otherwise.
  6. I sincerely love networking (still), and don’t have any interest in doing anything else. There’s so much more to learn and know, as well as ways to contribute to the community. I see the CCDE as a way to get deeper into the belly of the beast.

Despite all of those very good reasons to go after CCDE, I believe that the program will be a challenge for me to complete.

  1. Time is a big problem right now. I have, effectively, two jobs. My day job is as a global network engineer on a small team, where there’s a lot of work to be done and no one I can delegate to (although I’m working with the new guy, and my boss helps out when he’s not in his fifteenth meeting of the day). I’m responsible for all of the backroom infrastructure – routing, switching, security, LAN, WAN, wireless, optimization, load-balancing, etc. Some weeks are mercifully quiet. Some weeks are intense. It’s a full-time job, to be sure. My other job involves creating content for the networking industry. I write for trade magazines, create and produce podcasts, edit a community networking blog, and also do much of the accounting work related to the business, among other things. There’s quite a lot to it. Between the two jobs, I’m not sure exactly how I’m going to make CCDE work. Yet.
  2. My background is that of an enterprise network architect and engineer. I have done nothing in the service provider space. Therefore, I’ve got some challenges in that there’s certain technologies at play I’ve never had occasion to use, and certain architectural problems I’ve never had to think through. Then again, that’s a big part of the point of going through the CCDE program. I want to get a handle on aspects of network design I’ve not done previously.

All of that said, I’m interested in forming (or participating in) a CCDE study group. I’m not sure how such a study group would work or make sense as yet. But I want to explore the option as a way to enforce progress in study, and discussion of CCDE practical issues. If you’re serious about the CCDE program and are similarly interested, contact me via ethan.banks@packetpushers.net.