Thought Leadership

forrester_SM_1204_blog_002

Subscribe to our blog

Your email:

Connect with Ness

Software Engineering Services Blog

Current Articles | RSS Feed RSS Feed

Can Microsoft or Blackberry break the iOS/Android Developer Stronghold?

  
  
  

by Ron Miller
Ness Blogger

BlackBerry and Microsoft's manufacturing partners have produced some compelling phones of late, but whether it will translate into phone sales is still unclear. One of the big driving success factors of any phone OS is how well developed the app ecosystem is and that requires an engaged developer community. So far at least, neither challenger has shown it can break the iOS/Android duopoly.

platform battle

Graphic by Tsahi Levent-Levi on Flickr. Used under Creative Commons SA license.

Not surprisingly, there is a connection between market share and the level of developer interest. Developers aren't stupid. They follow the money. 

A recent survey conducted by Vision Mobile really drove this home. For starters, Android, clearly the most popular phone OS, has drawn the most interest from developers with 72 percent now developing on the Android platform, up 4 percent from the 2012 survey.

While iOS dropped 5 points to 56 percent, Vision Mobile attributes the shift to an increase in mobile developers from Asia where Android has a strong market presence and a big population base. One interesting data point was HTML sitting at 50 percent. 

As for Windows Phone OS and BlackBerry OS? BlackBerry was stuck at 16 percent and Windows at 21 percent, both unchanged from last year.

Meanwhile, 74 percent of developers reported developing apps for 2 or more platforms, but as you would expect, iOS and Android were the most likely candidates here. In case you're wondering when it comes to prioritizing which platform to develop for first, in this instance, iOS is the winner with 42 percent reporting they develop for iOS followed by Android, probably due to the fact that developers tend to make more money on iOS.

developer platform popularity

Chart courtesy Vision Mobile

When BlackBerry made its big phone announcement yesterday, it went out of its way to trumpet the list of apps available out of the gate including Box, Evernote, Dropbox, Webex and of course the obligatory Angry Birds; but these are the developers with resources who want to be on every platform out there. The real measure of the platform popularity will come over time -- and if the overall developer mindshare can shift from those hardened market share positions.

The same goes for Microsoft, which of course has a head start with Windows Phone OS, yet doesn't seem to be able to move the needle much either. It too has the big players on board, but when I talk to people about phone choices, the perception is that there are not enough apps. Vision Mobile believes developers are waiting for the market to develop before fulling embracing, the platform, yet phone buyers seem to be waiting for the apps. Such a stalemate doesn't bode well for Microsoft, although Vision Mobile believe they have potential to do so because of their Windows market share.

The wild card here though is the growing smartphone market. This is not a fixed pie, and that means if it can grow, the potential is there for any of these companies (or others like Mozilla and Ubuntu for example) to gain market share. In fact, Vision Mobile reports the handset industry is growing at 23 percent CAGR and 700 million smartphones shipped in 2012. There is no reason to believe this trend will change -- but neither is there reason to be truly optimistic that the competition can break the iOS-Android one-two punch.

cell phone growth

Chart courtesy Vision Mobile

The survey was conducted over a 5 week period in October and November, 2012 and involved 3400 respondents from 95 countries, which is a fairly substantial and diverse sample.  

You should have a look at all the results because it's an intriguing survey, but the bottom line is developers are business people, and are for the most part no different from any other business, motivated by money and success -- and unless BlackBerry and Microsoft can find a way to lure users in much larger numbers to use their phones, getting developers on board is going to continue to be a major challenge for both companies.

5 Links for Developers and IT Pros 10-26-12

  
  
  

5 10 26 12It's Friday and that means it's time for our weekly feature where we search the Web looking for 5 interesting, funny and poignant links for developers and IT Pros.

If you missed our most recent post, The Disappearing Cloud, please check it out now. A recent survey found that while most people don't understand the term "cloud computing," they use cloud services -- and that's fine, they don't need ot understand industry buzz words.

Please consider subscribing if you like what you see here, and if you have something to say, please feel free to leave a comment and let us know what you think.

And without further delay, here we go with this week's links:

IT budgets up, but salary cuts still a concern: study | Network World

The good news is that a study by Society for Information Management finds that average IT budgets increased this year, and salaries increased for 60 percent of IT according to the study, but 16 percent of IT pros had to endure salary cuts so it's not all sunshine and light.

A Progress Report on HTML5 Apps Platforms | Dr. Dobbs

The enthusiasm for an HTML5 app store was strong last year, but this year it seems to have waned as developers started working in earnest with the platform. It doesn't mean it's not going to happen, but the pace has slowed and may actually move away from the storefront idea back to the browser. (Not sure why you can't have both as with the Chrome app store.)

Google Compute Engine Is Gonna Change The Public Cloud Game | Cloudave

Could the Google Cloud platform challenge the likes of Amazon Web Services (AWS). This writer thinks it's possible. He tested the platform and found that he could set up instances almost instantly and he believes this along with a simple administrative interface could be attractive to IT pros, which could draw business from AWS. We shall see.

Hackers, Security Pros Talk Penetration Testing, Social Engineering | CIO.com

Going to a security conference is bound to make you paranoid and CIO says they sent reporter to the GrrCon to get the low down. Read this post to find out what he learned about protecting your system from hackers.

Java still has a crucial role to play—despite security risks | Ars Technica

While many worry about security vulnerabilities in Java, it's so widely used by so many useful web services, it's difficult for users to shut down the Java Runtime Environment in spite of the risks.

Photo by Tomma Henckel. Used under Creative Commons Share Alike/Attribution License.

Tags: , ,

Smart Companies are Going Mobile First

  
  
  

2736798185 19057c22eaFor a long time, developers looked at mobile as an afterthought, something to be done after the web site, but increasingly they see the value of a mobile-first approach as we see the proliferation of more and more mobile devices in the world.

As the number of mobile devices increases, it only makes sense to put mobile in the forefront as the key screen, but it's sometimes hard for organizations to see that. At a session at the recent Landmark’s Media Tech Summit in New York City, Ness Chief Innovation Officer, Neil Fox chaired a breakout discussion on mobile application development entitled "Mobile Development – Destiny or Distraction."   

According to Ness VP of Education, Publishing and Media Todd Sirrine who attended the session, it featured wide-ranging discussion of issues facing mobile developers with the concept of ‘mobile first’ development being a sea change shift in product development planning at the center." As Sirrine reported, "Mobile and Tablet design now sit at the forefront of product engineering discussions, rather than being an element that would be added later on."

And for good reason. Ars Technica recently reported that there are now 6 billion cell phone subscriptions in the world. While it's important to make the distinction between users and subscribers, and many people have more than one subscription, it illustrates just how fast mobile is growing. And as the price of smart phones drops, the number of phones will likely increase.

That means that you have to be thinking in terms of mobile delivery if you want to reach people on the device they are most likely to use. As people move away from desktop computers, that device is the smartphone. At a talk last week at the BoxWorks Conference, Clayton Christensen, author The Innovator's Dilemma, described the shift from Mainframes all the way to PCs and now to mobile, and that with each shift, it changed the way we delivered content and software to users. Today, as mobile devices continue to proliferate, and provide the ability to carry this computing power with us, it can't help but have an impact on the way developers build software. 

This was made clear at the Gilbane Conference last December when Ektron CMO Tom Wentworth gave a talk called Thinking Mobile First.  He described the 4 Fs of mobile maturity as Mobile Failure, Mobile Focus, Mobile Friendly and finally Mobile First. You have to ask yourself where you are on that continuum today and how you can get to mobile first soon.

4 fs of mobile maturity

Slide courtesy of Tom Wentworth. Used by permission.

If you are simply displaying your web site on the small screen and forcing your users to pinch and scroll to see anything on the page, you have a very long way to go. If you have gotten to the point of providing a mobile experience that's distinct from the web site, you are getting there. If you have optimized for mobile including building in support for touch gestures and leveraging the capabilities of the device such as geolocation and camera, you're where you need to be.

If you want an example of this, look at what ESPN is doing around its mobile first strategy.

Beyond that, analyze your company's mobile strategy and if you're not putting mobile front and center, check out the device trends and think about why not, because the sooner you concentrate on mobile, the more people you are going to be able to reach

 Photo Credit: TimShoesUntied on Flickr. Used under Creative Commons License.

Survey Suggests Facebook Could be Right About HTML5

  
  
  

7594555062 0047ca781fA recent survey of over 5500 Appcelerator developers conducted by IDC found that among other things, developers aren't thrilled with HTML5, a data point I found surprising until you really examine the data.

You may recall that earlier this month I wrote about Facebook's decision to abandon HTML5 and move to a native app environment -- which by the way has been our most popular post this year to date. At the time, Facebook appeared to be an anomaly among developers, but could Facebook's decision be a harbinger of a deeper dissatisfaction with HTML5 in the developer community? It might -- at least according to this survey.

The survey asked developers to rate their satisfaction with a number of HTML5 features and found that for the most part, they rated features on the "neutral to dissatisfied" spectrum. These included security, monetization, fragmentation and several other attributes. They were most unhappy with monetization with 83.4 percent answering on the neutral to dissatisfied spectrum, followed by Security with 81.8 percent.

In fact, the only elements the survey found where developers were actually happy with HTML5 was cross development capabilities, which 83.4 percent reported that they were satisfied with -- and immediate updates, which 81.8 percent were satisfied with -- both of which are clear advantages of using HTML5.

The strange part of this survey though is that IDC chose to lump neutral responses with dissatisfied ones. Unless we see a breakdown of how those two responses split, it really is difficult to to draw any firm conclusions from these results. Neutral, after all, is very different from dissatisfied. In one you have no real feelings one way or the other and with the other you are unhappy in some fundamental way.

So if developers weren't putting their energy in HTML5, where were they putting it? 85 percent reported developing for the iPhone with 76 percent developing for the Android phone. And for all the talk of being unhappy with HTML5, 66 percent of respondents were still developing for the HTML5 mobile web. If you're wondering where Windows came in on this, 21 percent reported developing apps for Windows phones -- which doesn't bode well for Windows moving forward. Even worse was Blackberry phones with just 9 percent of developers creating apps for the Blackberry.

So given the data in this report, how do you account for the broad difference in perception around HTML5 and the reality this survey purports to paint? It could have something to do with lumping neutral and dissatisfied into one category, and it could have to do with the sponsor of the survey, which makes cross-platform mobile development tools. When it comes to vendor-sponsored surveys, I always give the caveat that the sponsor is looking to show a result that puts their products and services in the best possible light or illustrates a need that the sponsor's company can fill.

It could also have to do with Appcelerator customers, who were surveyed for this report,  and how as a demographic, they choose to distribute their development resources. In spite of the fact that this survey included such a large number developers, it's still hard to draw firm conclusions about it from such a homogenized group.

When it comes to HMTL5, Facebook may be an abberation or it might have recognized something more fundamental about HTML5, but we'll need more data to find out.

Photo by yukop on Flickr. Used under Creative Commons License.

Facebook Abandoned HTML5 -- Should You?

  
  
  

2331979671 d8f1024c3cWe've written here before about the battle between the browser and the native app and we understand developers have very strong opinions about this. That's why it was so interesting that Mark Zuckerber speaking in an interview at TechCrunch Disrupt yesterday admitted that going with HTML5 and open web standards was a huge mistake.


Zuckerberg believes his company lost valuable time while focusing on an HTML5 development path. "It took us 6-8 months to build FaceWeb [the mobile HTML5 version of Facebook], another 4 months or so to decide it wasn't going to do it after we kind of committed to that, and then we had to start over over and start rewriting everything to be native," he said.

He added, "We burnt two years and it's really painful, and I think we will probably look back and say that it was one of the biggest mistakes, if not the biggest strategic mistake we could have made."

That's quite a revealing comment. Zuckerberg and his company had committed to an open approach using HTML5, then found it simply couldn't keep up with the the kind of demand that Facebook users had. Anyone who has used the iOS app before the update can tell you that it was painful to use. It's better now, but still too slow in my view (maybe I'm just impatient).

Glenn Gruber, avp of travel technologies and mobile solutions at Ness thinks Facebook's might have taken this strategic approach with HTML5 because of a desire to pursue a purity of vision about about write once, deploy everywhere, which HTML5 represented. But when it came to executing, it turned out HTML5 couldn't handle Facebook's tremendous performance requirements.

Gruber believes that for Facebook, HTML5 was great in theory, but turned out to be not ready for its needs in practice. "What I think that they missed is that while performance of HTML5 might not be too bad for some apps, the cumulative amount of time that people were spending on Facebook made the performance challenges very visible and then downright unacceptable," he said.

And that could be the strategic mistake Zuckerberg was referring to. I'm still left wondering why Facebook didn't simply pursue a parallel development path, but if as Gruber suggested they had bought into the idea of write once, use many times; once they committed to that approach, it took time to realize it wouldn't work.

It's a valuable lesson for all developers. When you commit to a given approach, you have to live with the results and sometimes there are unintended consequences. Most companies don't have the luxury of Facebook to do an about-face without suffering financially.

Purity of vision is great in theory unless it comes back to bite you in the butt in the end. That doesn't mean you shouldn't pursue HTML5 because not everyone has Facebook's performance requirements, but it's something you need to consider before you decide how to proceed.

Photo by Andrew Feinberg on Flickr. Used under the Creative Commons License.

Gartner Hype Cycle Report Predicts HTML5 Still Years Away

  
  
  

The most recent Gartner Hype Cycle report was not terribly optimistic about the future of widespread HTML5 adoption. In fact, according to the chart below, HTML5 is in Gartner's terms near the peak of "Inflated Expectations" and is 5-10 years away from being a legitimate business tool.

Gartner Hype Cycle Graphic
Gartner Hype Cycle Graphic - Courtesy of Gartner.

I think that is probably news to the many developers who are developing applications and web sites using HTML5 technologies today, and the browser developers who are building support into the major browsers. Either there are a lot of cutting edge developers out there or Gartner's not quite right on this one.

According to Todd Anglin, vice president for HTML5 Web and Mobile Tools at Telerik, a provider of productivity tools for software developers, HTML5 is actually developing at what he called "breakneck speed" and he seemed surprised by Gartner's prediction.

"The evolution of HTML5 is happening at breakneck speed and is being done with unprecedented collaboration amongst the biggest tech players," Anglin said. These include Microsoft, Google, Apple, Adobe, Amazon, SAP, and Facebook. Any time you can get those large companies all pointed in the same direction on any technology, that's going to be a major boost and with that kind of clout, it seems unlikely it will take as long at the Gartner graphic suggests it would.

As Anglin says, "This agreement on a single platform has never been seen before in software development, and as a result, it is possible that Gartner's hype calculations are poorly calibrated for HTML5."

As an example, Anglin points to Facebook, which has begun developing in HTML5 because of the flexibility it gives them.

"Even as Facebook announces a transition to native iOS apps, developers should note that the new "native" Facebook apps still include HTML5 in sections where Facebook wants the ability to change things more quickly. In other words, even in native app development, HTML5 is used to afford more flexibility and speed to the development process. And this is for a company that has the time, money, and talent to justify building native apps for all platforms," Anglin explained

What's more, Anglin points that in some ways Gartner appears to be contradicting other HTML5 predictions it has made in the past. "The 2012 Gartner Mobile Magic Quadrant report plainly states that 80% of all mobile apps will use HTML5 by 2015, a mere three years from now. Gartner is sending mixed messages with these reports, further underscoring the the challenge of properly estimating the success of HTML5," he said.

It seems clear that when Gartner's data is contradicting itself, and our own eyeballs tell us HTML5 is much more than hype, that perhaps the Hype Cycle just got it wrong this time. Rather than being 5-10 years from business using this on a regular basis, or even 3 years away as Gartner's other report suggested, it seems when just about every major technology company on the planet is getting behind HTML5, it is far more popular today than this graphic would suggest. 

5 Links for Developers and IT Pros 8-3-12

  
  
  
5 8 3 12It's Friday and that means it's time for our weekly feature where we search the Web looking for 5 interesting, funny and poignant links for developers and IT Pros.

If you missed our other post this week, HTML5 Fork Could Raise Developer Concerns, please check it out. When word emerged last week of a split between the two standards bodies charged with defining the HTML5 standard, it would be natural for developers to be concerned, but the impact of the split depends whom you ask..

Please consider subscribing if you like what you see here, and if you have something to say, please feel free to leave a comment and let us know what you think.

And without further delay, here we go with this week's links:

How HTML5 Video Works | Input Output

You may be ready to move on from Flash, but are you ready for what's coming next? This article covers HTML5 video in great detail giving you the knowledge you need to understand it better.

15 Code Editors For the iPad – For Free or Very Cheap | Smartbear Blog

With the iPad making inroads into the enterprise, it only makes sense that coders will start using its intelligent touch interface too. This article gives you an overview of 15 code editors, and you can't beat the price (after you invest in the iPad, of course). But it's further justification for buying one: you're using it for work.

VIDEO: Cloud Services: No Buzz, No Bull | Tom's IT Pro

This brief video gives you a short and sweet overview of cloud basics including the different types of cloud services and some vendor examples. It's not a lot of details, but it's a good starting point if you need a Cloud Computing 101-level understanding.

A Simple PaaS Comparison Guide (With the Java Dev in Mind) | Cloud Zone

Once you have a grip on the types of cloud services, if you want to focus on Platform as a Service (PaaS), this article gives you an overview of the types of services you are likely to find from a PaaS provider, then evaluates several of the major ones based on a common set of criteria. If you're confused about vendor selection, it's a good place to start.

The 9 most endangered species in the IT workforce | InfoWorld

While this article uses humor to make its point, the fact is that a lot of these IT jobs could be going away. It's all part of the evolution of any business. You probably don't see many COBOL programmers around your company anymore either. Nonetheless, you may want to have a look to see if you're on the list just to cover your bases.

Photo by Ron Miller Used under Creative Commons Share Alike/Attribution License.

HTML5 Fork Could Raise Developer Concerns

  
  
  

7087270549 c5cc2e9bc3When stories emerged last week about a split developing between the two standards bodies charged with defining the HTML5 standard, it would have been natural for developers who have been trying to keep ahead of the curve to worry, but it could be that the standards bodies have less impact than you think on the browser developers.

For some background, stories began surfacing last week that the two main standards bodies, the WC3 (World Wide Web Consortium) and the WHATWG (Web Hypertext Application Technology Working Group) had reached a parting of the ways. As Steven J. Vaughan-Nichols wrote on HP I/O, WHATWG was developing what they call " the canonical description" and WC3 was more focused on "developing a snapshot" using the tried and true process they have followed over the years.

Vaughan-Nichols said it sounded like a fork to him, but does it matter to developers? That's the key question. Todd Anglin, vice president for HTML5 Web and Mobile Tools at Telerik, a provider of productivity tools for software developers, says there's probably nothing to worry about here.

"With the recent “split” between the W3C and WHATWG, there are fears that this change will lead to an “HTML5 fork” or chaos for developers. Instead, it is a good time to step back and remember that standards bodies like the W3C and WHATWG have very little impact on the version of “HTML5” shipping in browsers," he explained.

He says it's really up to the browser developers to work this out and as long as you can work across browsers, there won't be anything to worry about. "A standards body ultimately produces a recommendation, not a browser. For standards to matter, it remains the commitment of browser authors, like Google, Apple, Microsoft, and Mozilla, to ship browser features that interoperate. And there is no indication that commitment is changing," Anglin said.

Meanwhile, J. Schwan,  founder and president of Solstice Consulting, a mobility consulting firm says it's true, it's about the browsers, but he thinks it could slow browser development around HTML5 and this could make cell phone app development environments more important. "What this does mean is the pace of browser adoption/standardization of web technology capabilities may further decrease; therefore mobile web capabilities will continue to lag behind native mobile software development kits (i.e. iOS SDK, Android SDK). Over time, this will further widen the gap between native mobile app and mobile web capabilities, continuing to make native apps the preferred end user experience," Scwan said.

Anglin is not so sure about that, saying that the approach browser developers choose to use has a lot to do with the pace of the HTML5 development and some of it at least will continue to be rapid. "The most likely impact of this decision will be different definitions of “HTML5 ready.” As we already see today, companies like Google and Mozilla race into the future, implementing and “standardizing” new HTML5 features aggressively, and they will use the WHATWG definition of HTML5 to define a “HTML5 ready” browser. Meanwhile, Microsoft is likely to continue its slower pace of evolution with Internet Explorer, and they will find shelter in the W3C’s snapshot to claim IE is HTML5 ready."

Whatever happens to the HTML5 standard development from here on out, it does appear to be taking two different approaches. That could help app development environments as Schwan thinks, or it could be be as Anglin thinks more of a browser issue with little impact on developers. Time will tell.

Graphic by codepo8 on Flickr. Used under Creative Commons License.

5 Links for Developers and IT Pros 7-27-12

  
  
  

5 at Frankfurt AirportIt's Friday and that means it's time for our weekly feature where we search the Web looking for 5 interesting, funny and poignant links for developers and IT Pros.

If you missed our other post this week, No Surprise Mobile Programmers Making Big Bucks, please check it out. The Boston Globe recently ran a slide show of what it considered surprising 6 figure jobs. Mobile programmer was at the top of the list, but given the special skills required and the demand for talent, it hardly seems surprising.

Please consider subscribing if you like what you see here, and if you have something to say, please feel free to leave a comment and let us know what you think.

And without further delay, here we go with this week's links:

Vint Cerf, Vampire Slayer | Input Output

Vint Cerf helped develop the protocols that created the Internet as we know it, so when he speaks you should listen. In this piece Cerf warns that the forces that brought you SOPA and PIPA, continue to try and undermine Internet freedom, and we must remain vigilant. He also talked about Al Gore's role in the development of the commercial Internet, international Internet growth and more.

Microsoft fixes 'big boobs' coding gaffe | BBC

Apparently some juvenile programmers decided to use this phrase every time they ran Microsoft's tool designed to work with Linux. The code name came to light when Linux developers discovered it, and Microsoft removed it. Needless to say it left them embarassed and further prolonged the programmer 'boy's club' stereotype.

HTML5: To Fork or Not to Fork | HP Input Output

Two groups, WC3 and WHATWG, have created a fork that has the potential to create two versions of the yet-to-be-defined HTML5 standard. It's hard to say if this is a simple division of labor where the two groups will eventually come together, or if it actually represents a philosophical split about how to develop the final standard. For now, we can only watch.

Closed for Business | Matt Gemmell

Matt Gemell brings up the problem of piracy in the Android software world, a problem that he claims is driving many Android developers out of business or forcing them to change their delivery model. He blames easy piracy, at least partly due to the open nature of the platform (even though he says he's an open source advocate), on reducing the motivation of developers to create for-profit programs for Android. Have a look. It's a compelling read.

5 Ways to Think Wisely in Development | Java Code Geeks

This post offers some sound advice to programmers on things to consider when making development decisions. When you read them, you may find that most of them apply to any decisions, not just programming design and development issues.

Bonus Link: 12 Outdated Songs Rewritten for Today’s Tech | Laptop Magazine

And finally, a bit of technology news fun as one writer takes 12 classic pop songs and rewrites the lyrics to remove outdated references (such as instead of Take a Letter Maria, address it to my wife; it's compose a text Siri). Have a look. It's a fun exercise.

Photo by Ron Miller Used under Creative Commons Share Alike/Attribution License.

5 Links for Developers and IT Pros 5-25-12

  
  
  
5 5 25 12It's Friday and that means it's time for our weekly feature where we search the Web looking for 5 interesting, funny and poignant links for developers and IT Pros.

If you missed our other post this week, Taking Control of BYOD Devices Without Destroying Personal Content, please check it out. The problem with bringing your own device to work is when you lose it and IT decides to remotely wipe your phone -- including your personal content. This week, I learned about two ways IT could control enterprise content while leaving your personal contact untouched.

Please consider subscribing if you like what you see here, and if you have something to say, please feel free to leave a comment and let us know what you think.

And without further delay, here we go with this week's links:

HTML5 Security Isn’t | Input Output

This is a deep dive into what you need to think about from a security perspective when you are creating HTML 5 applications. Don't assume you're secure. Get some knowledge and be sure.

Don't Store All Your Eggs in One Basket: An Idiom for the Cloud | Cloud Zone

Remember the old chestnut about never putting all your eggs in one basket? The implication of course being if you drop that one basket, you've lost all your eggs. This author argues, that even though Amazon is really cheap, and easy to provision, you would be wise to have redundant storage on other sites in case something goes wrong. It's always been sound advice and it remains so.

Build your own open-source cloud with ownCloud 4 | ZDNet

The head is a bit deceiving in that you can't apparently build just any cloud app. This open source approach though is worth exploring if you want to host your own file syncing and storage service. Just this week, EMC bought such a service called Syncplicity, but if you are concerned about security, regardless of the vendor, roll your own sync and share service and run it on your own servers. That way, you have nobody to blame but yourself if something goes wrong.

Fashionistas (and bureaucrats and journalists): Please learn to code | Dan Nguyen's blog

Last week, we linked to a story suggesting that the everyone-should-learn-to-code movement isn't such a good idea. This writer thinks that was a wrong-headed column and his answer, is that of course everyone should learn to code -- the more, the merrier.

Surveys Show Enterprises Both Embrace and Fear BYOD | Cloud Commons

Apparently when it comes to BYOD, IT pros love it and hate it -- at the same time. On one hand, if employees are bringing their own devices, that's one less thing for IT to worry about, yet they are still responsible for security and governance (oh and linking it to back-end systems), so there's a control problem here. Lot to like. Lot to worry about. Could be a wash.

Photo by Tomma Henckel Used under Creative Commons Share Alike/Attribution License.
All Posts