Massive Disruptive Change

I came across a number of web news reports that though unrelated indicate the massive technological changes that are occurring now and also going to sweep through our society over the coming years.

·         Borders, Angus & Robertson go bust

·         VMware Android handset virtualization hands-on

·         Nvidia Kal-El: Quad-core coming to a mobile near you

·         AeroVironment/DARPA’s Nano Hummingbird reconnaissance UAV

The bookstore bust story is likely more nuanced that just an “Internet kills books” meme but there’s certainly a strong effect there. I do love reading books on multiple Kindle devices rather than have to lug physical books around. Any business that is fundamental selling “data” – read software, music, movies, books just needs to stay away from high priced real estate commitments and high staff numbers.

VMware’s getting into virtualization for phones is strategically brilliant. The processing power coming down the road for handsets is mind blowing. People want to control their own phone environment, have one phone and businesses want their staff to use a controlled environment on their phone. It’s a perfect storm for a new virtualization market. It’s also another reason to use Android in business unless companies such as Apple, Microsoft and RIM don’t move quickly to provide something similar. Sure battery usage is an issue, but don’t under-estimate how quickly things are going to change on the processing power versus power usage equation.

Now the news on the Nvidia Kal-El Quad-core processor for phones and other devices put Microsoft’s plans for running Windows 8 on ARM and other SoC (System on a Chip) architectures into perspective. At first I thought it was a terrible idea and an indication of an ivory tower syndrome in Microsoft decision making. The thought of the current Windows desktop UI on phones and ipad like devices is ridiculous given the experience with Windows Mobile. I was hoping for an announcement of a Microsoft ipad like operating system building on what they’ve done for Windows Phone 7. However, looking at the upcoming power of these non-Intel SoC architectures, it looks more like a defensive move by Microsoft. Unless they’re in the game with respect to hardware like the Nvidia Kel-El gear, their crown jewel Windows will be under threat.

The last link in this unrelated set of technology links, is the Nano Hummingbird. Freakin amazing technology. All of this new technology changes our lives totally and the way we thought businesses and business processes worked up until now will change totally and quickly because of it. Another technology boom is coming once the broader business population get a feel for how much this new technology will change the business landscape (followed by the inevitable bust when people get over exuberant as we as a collective always do).

http://apolon.torqsoftware.net/

The Power of Relationships

The Gephi blog has a post on the Egyptian political changes in relation to Mubarak:

The Gephi dynamic visualization of the twitter relationships reminded me of the work we are doing on the MVX Object Server functionality. The MVX Object Server leverages the power of relationships between the information in your SCADA and Industrial Automation systems. Check out the following video that runs through how we use object oriented relationships and network graphs to extend the expressive power of systems beyond that possible with tag/point based software:

http://www.youtube.com/user/TorqSoftware#p/a/u/5/ffhgsWPgQNU

http://apolon.torqsoftware.net/

Wording Habits

It’s just the way of the world, but clients and potential clients of software development often use particular wording in order to imply that some work should be very inexpensive to complete. Here’s just a few examples from last couple of weeks that were infuriating and humorous all at the same time:

·         “Minor modification needed”. Often a change is clearly a minor modification, but in many functionality areas these words shouldn’t be used until at least a short investigation is undertaken.

·         “Can this be fixed?” in reference to a functionality item that was never mentioned before. When it’s totally new functionality being requested, it’s not a fix, its new work!

·         “So users can finally do X” in relation to an IT initiated environment change where users could do X with no problems before the environment change.

·         “for a very standard X environment” implying it’s going to be a small task to implement.

Yes, I’m bitching here and its pathetic. I just think trying to pre-emptively minimize a task by using wording that implies the task is small is counter-productive for all parties. It may well be a small task, but let’s figure that out together. We are likely to arrive at a unique solution that is both inexpensive and satisfies all of the requirements.

PS: I’m sure Software Developers unconsciously also use terminology that highlight the uncertainty of software development estimates which frustrates the crap out of buyers of software development services.

http://apolon.torqsoftware.net/

Nokia changes its CEO and its tune

The machinations at Nokia are fascinating:

http://www.engadget.com/2011/02/08/nokia-ceo-stephen-elop-rallies-troops-in-brutally-honest-burnin/

When the previous CEO was regularly coming out with put downs targeting the Android platform, I was thinking “What planet is this guy on?”. Is he in the same reality as the rest of us?

The new CEO is at least acknowledging that they are losing ground big time. The pattern of the head-honchos at large companies getting comfortable with a view of world and then being shocked when that view crumbles because of some technology or market shift is such a common one. Ivory towers anyone?

http://apolon.torqsoftware.net/

First 5 minutes with a Kindle DX

I purchased a Kindle DX and just got it today. The unboxing experience was interesting in that it had a few of the typical peel off tabs that are typical with gadgets and electronic equipment. For some reason I thought that the front screen showing the first two steps (plug into power and then turn on) was another sheet to peel off. It took me a couple of seconds to realize that the first step instructions was the actual Kindle screen. This is a sort of screen-culture shock which made me smile once I realized it. The next culture shock was that I was looking for where to configure the Wifi. Instead it just worked and started downloading my books from the local cell towers with need to configure settings or deal with a phone company on my part. Very nice startup experience and impressive. I put no effort into understanding how a Kindle DX operated beforehand or the premises on which it operated. It was all just discovered in the first five minutes.

http://apolon.torqsoftware.net/