Be wary of using your iWhatever on public networks until the patches are made. The scary part is not knowing how long the “bad guys” have been exploiting this.
For all the bad rap BlackBerry got for their product, one thing that they never compromised on was security. From device, through the phone carrier, through the BB data center, over the Internet, and to your company’s mail server.
The Lotus Forgot series: An alternative to a full Designer client on Mac or Linux and lesson on who develops applications
We don’t need a Designer client for the Mac or Linux. We need one for the people.
I understand the effort to create a full new instance of the designer client on a different platform is a daunting task. And in the end, who might use it? Developers. Some of those developers will use Macs at work. Some will be college and high school students. Some will be computer-savvy small business owners and entrepreneurs who serve as the CEO, CIO, developer, and user all in one. From IBM’s perspective, this may seem a rather small niche to dedicate the resources. It’s about ROI. So I propose a solution that would reach a much larger market and have a broader impact in enabling people to serve their own simple development needs:
Add basic development functionality back into the Notes client.
Yes, make the Notes client as it once was in the days before R5 when the ability to create applications was an integral part of the Notes client. What would it include? View development (which is already there), Formula language (which is already there in some capacity), and form development. Some agent development probably too. Provide people with enough to be able to serve their own basic needs without overwhelming them with complexity.
Why do this? Simple. Empower the people. Power users have always existed. They were what made the early versions of Notes so successful. It was easy for them to create their own tools in Notes and they loved it. LOVED IT! I can recall many times in the R3/R4 days when users came to me with a database that they had created or made a copy and modified it and wanted to share it with other people on their team. I took it, maybe cleaned it up a bit, and put it on the server where their whole team benefited. This was the root meaning of collaboration: Not just sharing data, but sharing solutions. By the users, for the users. It was truly Rapid Application Development (RAD). Before they had Notes, people were doing this in 1-2-3, Access, FoxPro, etc. It is no coincidence that the Notes client began losing favor among end users as soon as they lost their ability to explore what Notes can do by creating their own applications. The greatest advocates of Lotus Notes are those who can create applications in it.
People did not stop creating their own applications when the designer code was removed from Notes. But now they just do it in other tools like Access and Excel. Sure, there is also Sharepoint and Quickr, but those do not provide for PERSONAL tools. People will not “play” there they way they do with other software. Sadly, while users today are far more computer-savvy than they were in the 1990’s, they are being denied the opportunity to apply those skills to their job, at least where Notes is concerned. As a result, Notes has lost its appeal. Users have been driven away to other tools and no longer know (and have no motivation to learn) what could be done in Lotus Notes. To them it is no longer a PERSONAL productivity tool. Now the only way to get an application in Notes is to request it from the gatekeepers of I.T. It’s like building a Lego kit and giving it to a kid and then saying they have to bring it to you if they want to build something different with the pieces. Sure, the designer client is “free”, but it is not given to employees and for the most part they don’t even know it exists or how to get it.
If we are sincere in our belief that the power of collaboration and Open Source is truly for the benefit of all, then it should be made accessible to all. It should not be hoarded by the professional Domino developers of the world. It should not be locked out by the administrator who doesn’t want the additional work to manage the applications nor the I.T. director who doesn’t want to deal with losing control of application development process and his feeling of importance. Do not waste time defending this practice with the “good ol’ boy” mentality claims like “But the users don’t know how to create good applications.” or “their rights must be restricted for their own good or for the good of the company.” This is Social Business. This is the definition of Web 2.0. (See video)
Eliminate the hierarchy, eliminate the red tape. Empower the people. The more you empower the people around you, the more successful you will be. The more they must depend on you, the less you will be able to achieve. It’s the axiom of good leadership.
IBM may never feel justified in creating a full-blown designer client for Mac OS or Linux. They may never go back to having the simple developer client for the masses that was so successful. So while you wait for IBM to decide what to do, I suggest this: Let your people know the designer client exists. Make the designer client available to anyone who asks for it. I would even encourage them. If you have any programmers in the company that code in other software, be sure to give it to them.
Notes was founded on the principle of giving people the ability to create their own custom applications. (The History of Lotus Notes) That principle has clearly been forgotten.
If you agree, please vote for this idea at IdeaJam