I have been an avid reader of science fiction. Issac Asimov and the Foundation Series has been my most favorite author and series. Now how is it related to this blog entry... because what I read in an e-Week today is literally out of science fiction...
The story titled.... "Storm Worm Botnet Lobotomizing Anti-Virus Programs" (Click here to read the article on e-Week)
The part which was scary enough was what the bot net called the "Storm" is able to do to Antivirus applications and other background processes like P2P programs but the scarier part was its ability to change is own signature every 30 minutes and its ability to detect intrusion by researchers and invoke attack against them!!!
If you ever imagined of virtual mafia,,, this is it. The trouble is that most of the owners of the machines participating in the botnet are innocent victims who fell prey to promise of free software or other incentives.
From the e-week article, I judge (hopefully correctly) that the botnet machines are primarily Microsoft Windows based machines but all machines are vulnerable to the Distributed Denial of Service (DDoS) attacks the Botnet unleashes.
There are few documented cases of e-extortion against popular websites and the e-Week article talks about a take down of an Israel based security company.
Now this has been an eye opener to what an application can face once it is put out in the wild. Thankfully, most ISPs today are equipped to handle DDoS attacks to some degree.
Application Security to most software designers today is an after thought. With composite applications and mash-ups becoming the corner stone of Web 2.0 applications in next few months, I believe application security deserves another look and should become one of the primary consideration with performance and usability while architecting any new applications.
Sunday, October 28, 2007
Sunday, September 30, 2007
Challanging Status Quo and Execution...
It is always nice to hear words like - "Challenging status quo..." in a mission statement, not many organizations actually take on the feat. Understandably so. There is always a risk in venturing into uncharted waters and success in one market does not always guarantee success in another.
The difference in having a grand vision and failed vision is really the - EXECUTION.
Let's turn to some successes in a field which I am not really familiar with but I am intrigued because the business model is dependent on the goodness of human nature. Hard to come by huh...?
The industry is - MICRO CREDIT or MICRO FINANCE. I started reading about its success in the possibly one of the poorest countries on earth - BANGLADESH. You expect with the scarcity of financial resources, there will be the obvious human nature to grab and run.
Well, that's what everybody thought, till Prof. Muhammad Yunus and Grameen Bank came along. Grameen bank serves the poor of the poor in rural Bangladesh. Uses an unheard of strategy - "Lending without collateral". Well, I can safely assume that since the individual loans were not very large, it would be less risky and the chances are the borrower would not have anything put as collateral anyway. But add up several thousands on those loans... the risk becomes enormous.
There are other strategy which Professor Yunus applied, which were so different from conventional banks, like focusing on women as borrowers than men... [Read more...]
So that was Bangladesh, but would the same hold true for some other market. I recently read in Atlanta Constitution Journal, about a success of Micro lending in Guatemala.
Ok... Ok... now where is the catch? You know, I will extend this example to IT field.
The points - I carry over from Micro Credit is - trusting the goodness of human nature and applying success from one market to another.
Offshore/Near shoring has proved beyond doubt that it is possible to perform software development work anywhere and anytime.
But it is also a sad truth is the same industry that lot of people have to work long hours. Some of it to obtain experience, gain customer confidence and business and explore new technologies but some because of lack of better term - "projects that could have been better managed". Having said that, it is nature of software development. Progressive elaboration is the inherent gene. The more people see, the more people want to make it better. So it is not always in the control of the stakeholders that software developers directly interact with.
The industry has worked hard to find solution for this issue as the software systems get more and more complicated. Instead of being an monolithic application in control of a single organization, we are now looking at the age of mish-mash, landing pages and composite applications. But that is a topic for a different day.
So back to the mantra of "work life balance". One of the enabler for work life balance is - "Telecommuting". There is no work in the world better suited for this enabler than - Software Development.
Now, back to my argument goodness of human nature. The belief more often than not, people will try to do the right thing.
The argument, if it works in western countries, it MAY not WORK in an offshore environment. My argument - is to believe in the GEEKy nature of software development. A Geek is a geek not matter where s/he is let loose. A geek takes pleasure in getting things accomplished and doing it well.
Software Development is a field of knowledge workers. It is in the interest of the a software development organization willing to grow to attract and retain the best of the lot and for the right reasons.
Now that we have a VISION of a global diverse and dispersed network of technology gurus, let's looking a possible execution model. Strangely enough, it is nothing new and is not alien to companies with ISO:9001 and CMMi level compliance.
It is the use of METRICS. Establish performance metrics and clear guidelines for telecommuting employees. For example:
On the flip side, there is a investment on the side of the organization in terms of raising the level of infrastructure. But what is gains is more productive employees in return.
From end of the employee, it is ability to save on a long commute time and ability to address family needs at times. The caveat is that the individual has to see this an incentive and not as a way to make the employee work longer hours. Also, the individual has to drop the sense of entitlement like getting company provided Internet connection just for telecommuting purposes.
All deals are based on give and take as long both sides understand the benefits.
Has it been done before? Yes, absolutely.
IBM touts of an global workforce which is built on flex hours and telecommuting. Read about the success at BestBuy.com, the online division of the electronics retailer in the US. (Read more on... "Smashing the clock"; Cover Story; Business Week - Dec 11, 2006)
If not true, anywhere else... true in India. Most women have tendency to take a break work in life changing situation like - marriage or having a child.
Though, whole premise of "work life balance", is giving priority to the family. But what if the organization is able to bring the talent back on no matter wherever in the world she is. It is a win-win situation for the employees and the organization.
Finally, a statistic recently published on concentration of IT/Software Development in India on rediff.com in the article - IT in India: Big successes, bigger gaps
The state of infrastructure in some of these cities may be something to write home about. But I can guarantee, if organizations based in these cities have probably already established telecommuting options for their workforce.
So for organizations, who haven't I would say wake up, before the heat gets turned on and this benefit becomes so... 2007.
The difference in having a grand vision and failed vision is really the - EXECUTION.
Let's turn to some successes in a field which I am not really familiar with but I am intrigued because the business model is dependent on the goodness of human nature. Hard to come by huh...?
The industry is - MICRO CREDIT or MICRO FINANCE. I started reading about its success in the possibly one of the poorest countries on earth - BANGLADESH. You expect with the scarcity of financial resources, there will be the obvious human nature to grab and run.
Well, that's what everybody thought, till Prof. Muhammad Yunus and Grameen Bank came along. Grameen bank serves the poor of the poor in rural Bangladesh. Uses an unheard of strategy - "Lending without collateral". Well, I can safely assume that since the individual loans were not very large, it would be less risky and the chances are the borrower would not have anything put as collateral anyway. But add up several thousands on those loans... the risk becomes enormous.
There are other strategy which Professor Yunus applied, which were so different from conventional banks, like focusing on women as borrowers than men... [Read more...]
So that was Bangladesh, but would the same hold true for some other market. I recently read in Atlanta Constitution Journal, about a success of Micro lending in Guatemala.
Ok... Ok... now where is the catch? You know, I will extend this example to IT field.
The points - I carry over from Micro Credit is - trusting the goodness of human nature and applying success from one market to another.
Offshore/Near shoring has proved beyond doubt that it is possible to perform software development work anywhere and anytime.
But it is also a sad truth is the same industry that lot of people have to work long hours. Some of it to obtain experience, gain customer confidence and business and explore new technologies but some because of lack of better term - "projects that could have been better managed". Having said that, it is nature of software development. Progressive elaboration is the inherent gene. The more people see, the more people want to make it better. So it is not always in the control of the stakeholders that software developers directly interact with.
The industry has worked hard to find solution for this issue as the software systems get more and more complicated. Instead of being an monolithic application in control of a single organization, we are now looking at the age of mish-mash, landing pages and composite applications. But that is a topic for a different day.
So back to the mantra of "work life balance". One of the enabler for work life balance is - "Telecommuting". There is no work in the world better suited for this enabler than - Software Development.
Now, back to my argument goodness of human nature. The belief more often than not, people will try to do the right thing.
The argument, if it works in western countries, it MAY not WORK in an offshore environment. My argument - is to believe in the GEEKy nature of software development. A Geek is a geek not matter where s/he is let loose. A geek takes pleasure in getting things accomplished and doing it well.
Software Development is a field of knowledge workers. It is in the interest of the a software development organization willing to grow to attract and retain the best of the lot and for the right reasons.
Now that we have a VISION of a global diverse and dispersed network of technology gurus, let's looking a possible execution model. Strangely enough, it is nothing new and is not alien to companies with ISO:9001 and CMMi level compliance.
It is the use of METRICS. Establish performance metrics and clear guidelines for telecommuting employees. For example:
- The employee must a proven and establish record of on time delivery and accurate reporting.
- The employee already must have high speed Internet access at home which s/he is willing to use for business purposes.
- The employee must possess a computer capable of remotely accessing the employee's desktop at work. The actual work will be done on the desktop at work.
- If the developer running late on a task on a weekly basis, s/he is prohibited from telecommuting.
- Allow limited days in a week for telecommuting as a starter.
On the flip side, there is a investment on the side of the organization in terms of raising the level of infrastructure. But what is gains is more productive employees in return.
From end of the employee, it is ability to save on a long commute time and ability to address family needs at times. The caveat is that the individual has to see this an incentive and not as a way to make the employee work longer hours. Also, the individual has to drop the sense of entitlement like getting company provided Internet connection just for telecommuting purposes.
All deals are based on give and take as long both sides understand the benefits.
Has it been done before? Yes, absolutely.
IBM touts of an global workforce which is built on flex hours and telecommuting. Read about the success at BestBuy.com, the online division of the electronics retailer in the US. (Read more on... "Smashing the clock"; Cover Story; Business Week - Dec 11, 2006)
If not true, anywhere else... true in India. Most women have tendency to take a break work in life changing situation like - marriage or having a child.
Though, whole premise of "work life balance", is giving priority to the family. But what if the organization is able to bring the talent back on no matter wherever in the world she is. It is a win-win situation for the employees and the organization.
Finally, a statistic recently published on concentration of IT/Software Development in India on rediff.com in the article - IT in India: Big successes, bigger gaps
Seven cities accounted for a whopping 95 per cent -- Bangalore (33 per cent), the National Capital Region (15 per cent), Chennai (14 per cent), Hyderabad (13 per cent), Pune (10 per cent), Navi Mumbai (8 per cent) and Kolkata (2 per cent).
The state of infrastructure in some of these cities may be something to write home about. But I can guarantee, if organizations based in these cities have probably already established telecommuting options for their workforce.
So for organizations, who haven't I would say wake up, before the heat gets turned on and this benefit becomes so... 2007.
Thursday, September 27, 2007
Sliverlight and Google Gears and AIR
Once again, it seems to the battle of the giants. Two fronts - Google vs. Microsoft. Competing technologies - Google Gears vs. Silverlight.
Both being browser based plug-ins to enable rich and compelling cross platform client experience. The grand vision is to use the web and desktop so seamlessly that the boundaries get blurred. But looking closely that's where the commonality ends.
Microsoft Silvelight(tm) seems to be more targeted towards delivering the rich client interface, a easy programming paradigm offered by Windows Presentation Framework (WPF) to the browser. Currently version 1.0 and 1.1 in pre-alpha, the vision is expected to be delivered to early 2008. Having said that, the developer tools available to enable Silverlight comes with Microsoft Visual Studio 2008 or a separately licensed tool as Microsoft Expression. Of course, this being true as I understand it now. Things may change as we get closer to release.
Google Gears on the other hand is shot at the basic limitation of a web hosted/delivered application. The limitation being, that web application DO NOT work offline. Google Gears provides components such as LocalServer, Database and WorkerPool to make the experience of being online or offline indistinguishable.
There is a third front too... from Adobe. While Microsoft Silverlight is intended to launch attacks into Adobe Flash (or latest avatar Flex) niche of compelling graphic content on the web, Abode has its eyes set on helping their loyal user base capture the desktop with AIR (Adobe Integrated Runtime).
All of these technologies use AJAX in some form or another and are founded on delivering updated content from the web.
It remains to be seen if any one of the destined to dominate the web or the developer community will find a way to leverage all these technologies to benefits the user. I can very well imagine an application which will user XAML to deliver content to AIR and where Google Gears is used to store local information which syncs with the backend when connected. But can the competitiors?
Both being browser based plug-ins to enable rich and compelling cross platform client experience. The grand vision is to use the web and desktop so seamlessly that the boundaries get blurred. But looking closely that's where the commonality ends.
Microsoft Silvelight(tm) seems to be more targeted towards delivering the rich client interface, a easy programming paradigm offered by Windows Presentation Framework (WPF) to the browser. Currently version 1.0 and 1.1 in pre-alpha, the vision is expected to be delivered to early 2008. Having said that, the developer tools available to enable Silverlight comes with Microsoft Visual Studio 2008 or a separately licensed tool as Microsoft Expression. Of course, this being true as I understand it now. Things may change as we get closer to release.
Google Gears on the other hand is shot at the basic limitation of a web hosted/delivered application. The limitation being, that web application DO NOT work offline. Google Gears provides components such as LocalServer, Database and WorkerPool to make the experience of being online or offline indistinguishable.
There is a third front too... from Adobe. While Microsoft Silverlight is intended to launch attacks into Adobe Flash (or latest avatar Flex) niche of compelling graphic content on the web, Abode has its eyes set on helping their loyal user base capture the desktop with AIR (Adobe Integrated Runtime).
All of these technologies use AJAX in some form or another and are founded on delivering updated content from the web.
It remains to be seen if any one of the destined to dominate the web or the developer community will find a way to leverage all these technologies to benefits the user. I can very well imagine an application which will user XAML to deliver content to AIR and where Google Gears is used to store local information which syncs with the backend when connected. But can the competitiors?
Subscribe to:
Posts (Atom)