Skip to main content

Social Networking and Brand Management

People who have known me for some time in real life or on the Internet know that I'm resistant to hop on the bandwagon whenever a new social networking fad hits. In fact, my wife has consistently harassed me by saying that I'll be the last human being to join Facebook. She and everyone else does not understand that I already spend far too much time reading the news (and the local newspapers hate me for it); posting on my favorite gaming website (www.teamwarfare.com); playing games; recording music; etc. I have no more free time in that I don't know what to do with myself, so anything new has to be added to the waiting list, prioritized, etc. Facebook would simply suck away so much time that all of the things I want to do now would suffer as a result.

So when I joined Twitter last week, it was equivalent to the Second Coming of Christ (my apologies if people consider that heresy) in terms of the surprise that people had when they saw me tweeting of all people. After all, Twitter is probably just as much a time hog as Facebook.

The difference between the two is in the value of the site. I could just as easily claim that LinkedIn is a time hog when you consider the time I would spend answering questions, sending messages to my network, etc. But any activity on LinkedIn is considered an investment since it yields a benefit for my career. Can the same be said of Twitter?

Absolutely. Recall the two part blog (part 1 and part 2) where I talked about things that could be done to ensure that you get the maximum benefit out of a professional networking site. In part 2, I specifically discussed how I use LinkedIn to ensure that my value as a professional is proselytized to the maximum amount possible. Twitter is an extension of these efforts since LinkedIn now has direct links to Twitter.

The difference between LinkedIn and Twitter is in how you use each site. Telling you what you already know, Twitter is great for publishing short statements about anything you want. Given the integration that many websites now have with Twitter, it's very easy to share an article on a relevant topic with your followers. Links to the article are frequently shortened (using a site like Ping.fm, Bit.ly, etc.) giving you as many characters as possible to put a short message.

Frequently, sites put a message (similar to the article's headline) there. But this is an opportunity for you to increase your value in the eyes of those that follow you. Accept the headline? No way. Put your own spin on things, and if you can provoke some thought before they click on that link then you will be perceived as having value in their eyes.

(A secondary benefit, more for someone who is going senile like I am, is that when you are ready to write your blog entry for the next week then you have a week's worth of things that you found interesting documented in your list of tweets over the prior 7 days. I definitely plan on taking advantage of this in the future. But I digress...)

So if you haven't yet embraced Twitter, "there's gold in them thar hills." And if you want to hear my thoughts on relevant topics, feel free to follow me @foolomon.

Popular posts from this blog

It's Easier to Fail at DevOps than it is to Succeed

Slippery when wet Since the term DevOps was coined in Belgium back in 2009, it is impossible to avoid the term whether in discussions with colleagues or in professional trade magazines.  And during the years while this movement has gained momentum, many things have been written to describe what elements of a DevOps strategy are required for it to be successful. Yet in spite of this, there is an interesting data point worth noting: not many organizations feel there is a need for DevOps.  In a Gartner report entitled DevOps Adoption Survey Results (published in September 2015),  40%  of respondents said they had no plans to implement DevOps and 31% of respondents said they hadn't implemented it but planned to start in the 12 months after the survey was conducted. That left only 29% who had implemented DevOps in a pilot project or in production systems, which isn't a lot. "Maybe it's because there truly isn't a need for DevOps," you say.  While t...

So What is this IPaaS Stuff, Anyway?

 In my last post , I discussed how no-code/low-code platforms fulfill rapid development of business applications - addressing the needs of the Citizen Developer (a Gartner term  first used around 2009).  I also commented on how this specific objective limits their ability to provide true integration capabilities, which require the flexibility to adapt to the myriad variations of infrastructure.  This is a concern because companies often have acquired legacy systems via M&A activity while simultaneously investing in new technology solutions, resulting in a mishmash of systems with multiple ways of accessing them. In this post, I'd like to examine how the needs of the latter group are met by describing some key capabilities that are "must-haves" for any company looking to execute on a digital transformation strategy.  In order to do this, let's define who the target user base is for such a technology platform. Disclaimer:   I work for MuleSoft (a division...

Application Development Done Right

In a previous article, entitled DevOps as the Ultimate Panacea? , I described how developing code without thinking about the current needs of the end user as well as the future needs once they've become accustomed to using your application ends up not only frustrating them but also can result in customer churn and ultimately lower revenues.  In this article, I'd like to describe something simple that I came across today that shows a definite degree of effort to do quite the opposite. Recently, we had a severe snowstorm, one with blizzard-like conditions, which is unheard of in central New Jersey.  Being responsible adults, my wife and I went to the grocery store to stock up on essentials (read:  chips, chocolate, etc.) in case we get stuck at home. As we were ringing up our order, the cashier mentioned to us that the store has a mobile application.  Since both of us are in technology oriented professions, we were skeptical about the need for a grocery store mob...