When we talk about social networking, even from a corporate and business angle, we are almost always talking about public social networks such as Facebook and Twitter. These networks allow people and businesses to join freely and interact freely. For a company, the public nature of social networking exposure is a highly desirable one, as a business’ Facebook profile can act as a brochure, marketing source, communications outlet, and white pages guide all rolled into one.

But, increasingly, companies are turning to a different kind of social network, an internal one, with the aim of accomplishing a different set of goals. With an internal network, a business is trying to foster communication between employees, not between the company and its consumers. It is further trying to establish a secure forum for open and honest discourse, not simply to advertise and promote the business. The objectives are undoubtedly very different ones, but the basic concept is the same. An internal social networking site, after all, acts as a sort of Facebook application that is specifically programmed for company employees.

Many companies have already begun using internal social networks. With the arrival of several new and highly-heralded social software applications, IBM Connections perhaps being foremost among them, this trend can only be expected to continue and accelerate in coming years. So, what are the benefits of having an internal social network? And what are the drawbacks or challenges? Let’s take a quick look:

The Benefits of Having an Internal Social Network

• Boosts corporate ingenuity. Employees can propose changes or ideas, and others can vote on them, meaning that great conceptions can come from anywhere in the corporation.
• Improves company cohesiveness. Having an internal social network provides a relaxed and communicative environment for employees, even while at work. This has been shown to boost overall cohesiveness, which in turn strengthens worker motivation.
• Satisfies workers. Workers overwhelmingly support the implementation of an internal social network. While many choose not to use it, others feel more satisfied, engaged, and content with their position within the company after taking part.
• Creates a one-stop communication shop. Employees with complaints, managers planning a meeting, or departments coordinating with each other can achieve tremendous efficiencies by using an internal social networking application. This application, after all, can be used for business as well as more frivolous uses.
• Enter the cloud. Cloud computing has taken off in recent years, and many companies are working to get on board. Having a web-based social networking application can help employees facilitate that transition.

The Drawbacks of Having an Internal Social Network

• Identity management. When asked to list a challenge of internal networks, companies that have switched over routinely note that managing the profiles and identities of employees can be a very difficult task, especially in the early going. The challenge is even greater when a company has several subsidiaries or different entities spread out over multiple countries.
• Technical challenges. Along similar lines, establishing and maintaining a network involves considerable time and effort on a technical level. Many companies, however, choose to outsource these services. Doing so saves time, but can add up quickly in costs.
• Security and monitoring. On an internal social network, employees may discuss a wide range of matters that the company would not want publicly disseminated. This means that the utmost security precautions must be taken in order to insure that the network is consistently and reliably secure. Furthermore, along these lines, the company needs to establish a monitoring policy. What can and cannot be said over the internal network? Who will determine and deal with issues of inappropriate conduct? Even in a professional environment, such challenges arise with surprisingly regularity.
• Productivity losses. A very real concern of those against internal social networks is that these networks only reduce employee productivity without provide any offsetting corporate gains. If employees spend all their time chatting with a co-worker across the office, they are only less likely to accomplish their work.

These are the major pros and cons of internal social networks. It is probably safe to assume that such networks will only become increasingly common in the coming years. Even so, it is important that a company carefully weighs the benefits and the drawbacks before implementing a network. While there are a good number of possible arguments for and against getting an internal social network, all these factors should ultimately be considered in light of the individual company’s needs.

This is a guest post from Samantha Peters. Samantha is a blogger who enjoys writing for tech and career blogs covering a topics such as social media within the workplace. You can find Samantha at TheTechUpdate.com, and on Twitter and Facebook.

Related articles

• Why Internal Social Networks Usually Fail (socialfresh.com)
• Solidifying the Social Media Bubble (regulargeek.com)
• A Look Back And A Look Ahead At 2012 (regulargeek.com)
• Employees on Social Networks: To Be or Not To Be… (socialmediaexplorer.com)

One of the biggest questions for the tech industry in 2012 is the fate of the Windows-powered smartphones produced by Nokia, one of the latest entries into the ever-diversifying smartphone field. I say the fate of the Nokia Windows Phones is uncertain because most American consumers have given their phones a big “meh” thus far. To put things in perspective, let me give you an idea of how little pull the Nokia Windows Phone currently has in the U.S. smartphone market. Right now you can get a Nokia Lumia 710 Windows Phone at a Wal-Mart for free. They’ve essentially become like any standard free smartphone provided by cellphone providers, and that’s not exactly a compliment.

But wait. There are two reasons why American consumers shouldn’t rule out the Nokia Windows Phone—namely, the Lumia 800 and 900 smartphones. The 800 model was released to rave reviews in the U.K. and in mainland Europe in late 2011, and now Nokia is planning to launch the phone in the U.S. along with the souped up 900 model. While Microsoft and Nokia hope for equal success in the U.S. smartphone market, it’s hard to say how their phones will fare here. Let’s take a closer look at what they have to offer.

Specs and the Windows Phone OS

Surprisingly, the currently available Nokia Lumia 710 Windows phone has decent specs. Powered by a 1.4GHz processor, the Lumia 710 can perform most of the basic smartphone tasks with relative ease. The phone makes it fairly simple for the user to surf the web, run simultaneous apps, draft emails, and so on. It has modest storage capacity with 8GB, nothing too special. The Lumia 800 and 900 series will boast more robust specs, but still nothing to write home about when compared to its smartphone competitors.

The 800 and 900 series, however, will also be equipped with something altogether new, the Windows Phone OS. Microsoft and Nokia executives and spokespersons have attested to the strength of the new smartphone operating system, claiming that it will bring new innovation to the way people interact with mobile devices. Microsoft has taken it’s time designing this OS, which will supposedly reflect a completely novel approach to the smartphone user interface.

The Windows Phone OS interface will basically look like a series of interactive tiles which represent the various functions of the smartphone. These smart tiles—supposedly more customizable and responsive than the apps we’re accustomed to seeing on smartphones—represent the foundation by which users will interact with their phone. Reportedly, these tiles will reflect up-to-date information on a variety of data, from up-to-date weather notifications to the latest news on your Facebook wall. The Windows Phone OS will be compatible with all Microsoft related platforms, including Xbox, Zune, and the Microsoft Office suite. Based upon the marked enthusiasm from tech enthusiasts and analysts, the Nokia Lumia 900 in particular may have a shot at taking the smartphone in a new direction.

An Apples and Androids market

While the prospect of a new revolutionary smartphone is exciting to ponder, one has to wonder how it will affect a market already dominated by iPhones and various Android phones. With speculation and curisosity about the eminent iPhone 5 at an all time high, and with a seemingly bigger and better Android phone coming off the conveyor belt every month, it’s hard to imagine where the Windows Phone will fit in. But perhaps people will respond well to the much-needed diversity (and quality) in the smartphone market. We have to wait and see what happens until the Lumia 900 is released within the next few months.

This is a guest post by Jane Smith from background check. She is a Houston based freelance writer and blogger. Questions and comments can be sent to: janesmth161 @ gmail.com

Related articles

• Smartphone Versus Tablet – Which Device Suits My Needs Best? (regulargeek.com)
• Twitter Should Cut The SMS Cord (regulargeek.com)
• The Future of Phones: Forever Unknowable (technologizer.com)

And all this business about apps is a real spoiler for suspension of disbelief. I’m clicking a link, expecting to learn more about what I was reading (that was certainly the author’s intent) but instead I get an ad for an app. If I seriously consider it, I’ve lost my train of thought. If I actually take the detour and install it, I’ve lost bigtime. The best way to minimize the loss is hit the Back button and skip it. But that’s a loss too. I clicked the link for a reason. And that was thwarted.

The main concept here is that if you provide links in your mobile application, then you should be linking to some information about the topic you were reading, not an advertisement for a different app. By itself, this complaint seems to be a bit of a stretch. However, he follows with another post a few weeks later that really explains his issue:

Every time around the loop, since then, the Internet has served as the antidote to the controls that the tech industry would place on users. Every time, the tech industry has a rationale, with some validity, that wide-open access would be a nightmare. But eventually we overcome their barriers, and another layer comes on.

Basically, Dave is seeing these mobile apps as trying to kill the web. If the app is trying to control interactivity by only supplying a “walled garden”, similar to what Facebook is doing, then the user really loses the power of the web. The core idea of linking gets lost in this scenario. However, what if the web is more than just links?

Prior to the last few years, people were very document-centric and reading HTML pages from a PC. Now, we have mobile devices that allow you to use the web whenever you want no matter where you are. We also had web applications that did not allow you to take your information elsewhere or integrate with other applications. Now, many applications use your Twitter or Facebook login in order to authenticate, and then post statuses or even create events in Facebook.

In order to support all of this integration, the web is evolving. The web is no longer just HTML. Last summer, I wrote about the rise of the API:

As the web evolves, much of that evolution will be powered by application APIs. Some of the APIs will be application specific, like the Twitter API, and others will be more generic like the various semantic web standards. All of these available APIs allow programmers to create more interesting applications, and potentially a new API layer on top of what already exists. What this means in the long term is that we are finally getting to the point where the semantic web had hoped to be, linking data between various applications and hopefully doing something interesting.

A web of links can be limiting when looking at applications. When looking at reading a news story, links make sense, but reading articles is only part of the web. By looking at the data available, we are starting to create a more interactive and informative web. Sarah Perez at TechCrunch thinks this could be moving towards a web of apps, but that post is more focused on mobile apps. As I said previously, mobile apps tend to be limiting in their own ways.

Think about the possibilities of using the various APIs that are available. I am not just talking about the social network APIs, I am talking about things like Freebase, a huge collection of data, or even data aggregator/providers like Gnip and DataSift. Using these services, developers can build interesting applications using data from various sources without worrying about what the Twitter API looks like.

These types of services provide a level of abstraction that developers are used to. First, you get the core APIs, then you start abstracting those APIs into something easier to use. Once concerns about low-level APIs are removed, developers can focus on being more productive with the new abstraction layer and start solving real problems. Once developers focus on real problems, that is when the real fun begins.

So, is the web just a bunch of links or are we finally getting a layer of abstraction on top of all of the web applications. This layer of abstraction is a normal evolution for developers, and we just need to ensure this is translated into more interesting applications.

Related articles from RegularGeek:

• Twitter Should Cut The SMS Cord
• A Look Back And A Look Ahead At 2012
• Plus Or Like, Choose Your Sharing Weapon

First, some background about my own journey into software development. When I went to college, my plan was to become a civil engineer. I took two semesters of physics and realized that the plan was not going to work. I found out that I really did not like physics, and to be an engineer you need a solid physics background. Thankfully, I did not need to decide on a major until my second year was completed, and I did some research. I had settled on Industrial Engineering, where I could take some engineering classes as well as some operations and finance classes. It sounded interesting enough, but I thought I might need some help getting a job when I graduated. So, I decided to take an introductory programming class.

This was not my first taste of programming. Like any geek my age, I had written some Basic on a TRS-80 during school. However, my first programming class was like turning on the light bulb. I quickly realized that programming was what I really wanted to do. I changed my major, eventually graduated and have had several jobs in our industry. I have now been coding professionally for over 17 years.

What does this have to do with whether you should become a software engineer? The whole story is not entirely important, but there are some points that need to be understood.

You must enjoy what you are doing. This is even more important in software engineering that some other industries. In many cases, software engineering is not a typical 9 to 5 job. It is fairly stressful as well. If you do not enjoy programming, the stress will demotivate you to the point that your code will eventually suck. I wrote what was meant to be a humorous post about the trials of the job in August 2010. It is supposed to be a joke, but in some environments those points are too true.

You can have some level of job security. In this economy, any level of job security is good. This does not mean that programmers always keep their jobs. We go through layoffs just like everyone else. However, there are a lot of available jobs and the industry continues to grow.

There is good money in software engineering. You may not see large wads of cash to start, but over time your salary will grow. If you look at salary surveys for different locations, senior level engineers can make $100,000 or more.

There is a lot of job diversity available. Do you like working with real-time devices like embedded systems? Mobile devices, like phones and tablets, are growing rapidly and there is a ton of development occurring in the mobile space. Web sites and web applications are continuously being built and require people to know UI development, some server side development and maybe even some database code. If you like to code, there are plenty of niches to explore.

What is your inspiration? Why do you code? Some people like the idea of creating something. Others like solving puzzles. You may like the fast feedback cycle in programming. If you have no inspiration for programming, you probably will not really enjoy the job.

Easier path to independence. Some people may not like the idea of being a wage-slave at some big corporation. Software development allows you to work remotely or build your own consulting business. This is easier than in many other industries, where working remotely is just not a possibility.

Obviously, there is no clear reason to become a software engineer. It is a personal choice and not some stereotype like introverted math and science lovers who are devoted Star Wars and Star Trek fanatics. To find out if you like programming, try writing some simple code. Do not try to build a significant web application or some mobile app, that is too much to start with. Look at some basic tutorials on learning a language and start coding.

Other related posts:

• 15 Tenets For The Software Engineer
• Programming Is About Keeping Basic Skills Sharp
• 7 Resume Tips For a Software Developer

Last year, I wrote about the following trends, with some new comments in italics.

• Mobile Computing: People thought mobile computing was big with the advent of smartphones. With the addition of tablets like the iPad, mobile computing got a big screen to play with. As we have seen this past year, mobile computing is definitely exploding, and is likely going to become the dominant platform for non-business usage.
• Tablets everywhere: Not only are tablets gaining a lot of acceptance, they have mostly replaced netbooks as the “smaller than a laptop” device. As the prices drop, expect to see dedicated eReaders convert into tablets similar to what the Nook is doing. Granted, this was an obvious trend and we have seen the recent release of the Kindle Fire and Nook Tablet. More tablets are being released every month, but not many have been successful. Pricing is the biggest obstacle, which the Fire and Nook are trying to avoid.
• HTML5: HTML5 gets included because it has such different capabilities than web sites currently have. There is huge potential with this technology and it can also blur the lines of web site and desktop or mobile application. HTML5 video is already replacing flash for many sites. With browser support increasing for all parts of HTML5, we will start to see more interesting applications. It has also become the cross-platform language of choice for mobile applications, which given the drive towards mobile, is very important.
• Instant information: This is the extension of my semantic web prediction from last year. As linked data and geo data become more standardized, more applications will include augmented reality-like functionality. Once acceptance of linked data and geo data is more mainstream, other data silos will follow. This trend has not really gotten started yet. We are closer to having more information at our fingertips, but 2012 will probably be the year for this trend.
• Always On: We thought people were always connected before, but the technologies are finally getting to minority report levels. We have the Kinect and other gesture-based interfaces, near field communication to enable proximity computing, and everything is being integrated with social networks. Gesture-based interfaces are being pushed more, and with the mobile growth our connectivity has definitely increased. Now, this combines with the “instant information” trend to move into the augmented reality space.
• A Massive Data Startup: The one prediction I will make is that some data startup will become huge. We have some players already in Gnip and DataSift, but 2011 is really the year of data and one company will have massive growth. This is the one trend that really seems to need another year to become as large as I suspected. Gnip and DataSift are doing well and maybe I am underestimating what they have done in the past year.

Now that we have reviewed last year’s trends, what trends should we watch in 2012? One important note about these trends is that mobile computing is driving almost everything.

• Mobile and Social Commerce: We have only seen the tip of mobile commerce. Next year should be interesting as we see more in-store mobile deals, price comparison shopping and augmented reality focusing on ecommerce. The social aspect will not be in recommendations, but more stores on social networks and the general integration of social networks with ecommerce stores. The one problem here is that someone’s digital wallet will be hacked.
• Digital Health Startups: With the rise of mobile devices, we can capture more data in more places. Carrying your medical history and a digital archive of your daily activity and food intake can change the way the health and medicine industries work.
• Big Data Usability: In the past few years, we have seen the rise of NoSQL tools but they are in the realm of the developer. 2012 will be focused on capturing and using the data in much easier ways. How about point and click building of a data capture process and some simple tools for analyzing the data?
• The Rise of HTML5: 2011 only showed part of what is possible with HTML5. This is so important that it gets a spot this year as well as last year. HTML5 is changing the way web applications are built, including mobile. So, yes it is that big.
• People Talk About Augmented Reality Again: Augmented reality applications were too early when they were released the first time. They launched before smartphones really exploded and tablets barely existed. Now, mobile is everywhere, data speeds are getting better and we have more information readily available. Part of this is made possible by linked data initiatives and the availability of social information.
• Digital Identity: Let’s face it, your digital identity is either your Facebook or Google profile. It has come to the point where most of the internet will require one of these two logins in order to use a service. Obviously, this is both good and bad, and bloggers will focus on the bad parts, obviously.

First, here are the comments I had on each language:

1. Lua – The language is seeing some good activity on GitHub and StackOverflow. It has a solid Tiobe ranking, but more importantly, jobs for Lua are becoming available. The relative trend for Lua is a great indicator that it is ready to go mainstream.
2. R – With data analysis and big data becoming a part of every web startup, languages catering to the data crowd will become popular. The job trend data will be the most interesting part to watch here.
3. Clojure – While not popular within the Tiobe index, it is popular in some programming circles. In particular, its job trend growth is showing that it could be posed for a big year of adoption.
4. Go – Only Tiobe really shows this as a popular language. It is not ranked well in the Dataist Tier, and job trends are not very reliable yet. However, with a parent of Google it may not need purely organic growth.
5. Erlang – This has been around for a few years and has decent trends all around. With the continued growth of real-time technologies like XMPP (eJabberd specifically), PubSubHubbub and others, 2011 could be a year where it becomes the next Python.
6. Scala – This is one of the interesting trends. Scala has a very good showing in the Dataist Tier, but is not really ranked in the Tiobe index. With the solid job growth trends and popular adopters (i.e. Twitter), Scala could gain a serious amount of acceptance.
7. Groovy – More than anything, I believe Groovy missed its window of opportunity. It is a solid scripting language with decent job growth trends, but how can it differentiate itself from Ruby, Python, Erlang and Scala?
8. Scheme – For whatever reason, this language refuses to go away and has even picked up some interest. Without decent job growth, we could be another year away from Scheme breaking out again, at least 30 years after it broke out the first time.
9. ActionScript – ActionScript is included in this list because of its high ranking on Tiobe and the Dataist Tier. However, the job trends do not point to good things for the language. It could be a temporary slump, so you should keep an eye on it next year.

So, the top 11 posts  written this year were:

1. 9 Programming Languages To Watch In 2011
2. Traditional Programming Language Job Trends – February 2011
3. Web & Scripting Programming Language Job Trends – February 2011
4. 5 jQuery Scripts To Create a Great First Impression
5. Twitter Stops Whitelisting Applications
6. Google Plus Looks Good But Needs An Application Platform
7. Traditional Programming Language Job Trends – August 2011
8. 13 Free GTD Online Tools For Mac Windows OR Linux
9. As A Software Engineer, Do You Really Like Your Job?
10. Google Sites Becomes A Real SharePoint Competitor
11. 36 Resources To Help You Teach Kids Programming

Why 11 posts? Well, the top post was written one day before the anniversary last year and most of the traffic occurred after the anniversary. The job trends posts continue to have a strong showing regardless of when they were written. The social posts still tend to appear but they are more programming related as well. This continues a trend from last year.

Other posts that were very popular from previous years:

• What Programming Language Should I Learn?
• 25 Free Google Analytics Alternatives
• Traditional Programming Language Job Trends – February 2010
• Traditional Programming Language Job Trends – August 2010
• Google Sites Automation With Apps Script
• Web & Scripting Programming Language Job Trends – August 2010
• 12 Things A Programmer Really Needs To Know
• 7 Resume Tips For a Software Developer
• Why Is Data So Important?

My total statistics at the end of year three show that I was already writing long posts:

• Months Blogging: 36
• Posts Per Month: 11 (400 posts total)
• Words Per Post: 851
• Total Words In Posts: 339528

I continue to go against common wisdom and write posts that are even longer:

• Months Blogging: 48
• Posts Per Month: 12.3 (180 posts this year, and 580 posts total)
• Words Per Post: 887
• Total Words In Posts: 514328 (174,800 words this year)

This year saw the introduction of my list posts (93 so far) in the Geek Reading category, and the subsequent demise of those posts with the changes in Google Reader. I do hope to restart those posts when I can determine the best way to implement them. Ignoring the Geek Reading posts, my blogging was technically slower than last year, with 87 posts or just over 7 posts per month. I continued the trend of writing far too many words per post, but people keep reading.

The other side of the blog statistic picture is the external statistics. This past year, the blog had solid traffic growth and good subscriber numbers. Technorati continues to change how their rankings work where my ranking in Technology and InfoTech seems to range from 500 to 5000 and 100 to 2000 respectively. Google changed how their search engine worked again, and that seems to positively impacted traffic to the blog. Feedburner finally dropped FriendFeed from the subscriber numbers, and it recently peaked at 3010 subscribers.

The social landscape continues to change as much of the social sharing has been wildly different than previous years. I no longer see traffic from Digg or Google Buzz, but I now see traffic from DZone, LinkedIn and Google+. Facebook and Twitter look to be mainstays in social for any blog.

As always, thank you for your continued reading and social sharing. Hopefully, this blog will continue to be useful to you.

The Subscribe button for websites works just like the button on Facebook; once clicked the user will begin seeing the public posts of the person they have subscribed to in his or her News Feed. The subscribe action is also shared — allowing others to subscribe directly via the News Feed stories, and further increasing viral distribution.

So, the subscribe button is Like 2.0, where they added “frictionless sharing” to the original Like button. By themselves, these two announcements seem like basic iterations of various product features. However, you need to look at these posts within the larger scheme of things.

Google is integrating Google+ with all of its products. Some people did not think adding a “social layer” on top of the applications would be a good thing, but we are being proven otherwise. The idea is very similar to the frictionless sharing that Facebook has been talking about. Being able to quickly +1 and share from other Google sites, like YouTube, and within GMail means that more activity can be generated easily.

Facebook is learning that the simple Like is not quite good enough. Sharing is the main way content goes viral. So changing the way Likes work, and making things move towards a full share helps with “viral distribution”. Obviously, making sharing easier would be a huge win for Facebook if users can control what content is shared with what people.

However, there are problems with both systems. Facebook has a huge user population. But the user sharing control is not entirely seamless. Groups and selective sharing are not really core to the functionality, but add-ons. Facebook users are also not used to sharing with groups as much as just sharing with people that are friends. Google does not have as many users, and has had its own share of privacy issues. However, their selective sharing circles have been baked into everything. So, once you started using Google+ you were always using Circles. But Google+ is not without problems. Business pages are still evolving after a very shaky start.

Both systems are providing frictionless sharing, while giving users some control over who sees what content. So, which system should you choose as a user and as a business, blog or website? Obviously, the answer is both, but whether either system wins comes down to how the integration points really work. The integration points are things like the plugins for websites and blogs, developer APIs to help build an ecosystem of third party applications, and the mobile platforms.

Website and blog plugins exist for both systems and only provide minimal integration. Third party applications and mobile platforms are where the systems can really try to differentiate themselves. Facebook’s API platform has existed for a longer time, and social gaming has really grown rapidly. Google+ is still developing their API, which has some glaring holes, but they started their platform push with social gaming in an effort to jumpstart development activity.

The difference may be found in the mobile platforms. Facebook has a solid API and some mobile applications. On the other side, Google has Android and its tight integration with all things Google. This could be a huge advantage for Google as the mobile industry, as well as Android adoption, is exploding. Google+ even has a very nice mobile application.

The APIs may be a large part of luring developers, but even developers want to get paid. Monetization will be a huge question when choosing between the platforms. Google has a history of trying to be more developer friendly than their competition, or at least not as controlling as their competitors. Facebook has already shown that developers can monetize the Facebook platform, with Zynga being the poster boy for Facebook monetization.

Will developers choose the winner, or will a huge existing user population choose the winner? Will ease of monetization point to a winner or will mobile integration be the key? Do we really need a winner or will these two behemoths decide to provide integration across the platforms?