Organic KM: Enterprise 2.0 Would Signal The End Of The Corporate KM Function
Having read it I was trying to imagine what The Pope would think of going back to paganism...
The aim of this blog is to capture recommended web resources for information system architects
...to the busy professional who wants to remain aware of trends in a rapidly changing world, yet not be buried under a mountain of information
In the meantime, in the Valley, young (and old) kids, oblivious to all these weighty questions are writing their own SOA in very small letters - in mashup camps
Over the course of two days, more than 300 people turned up for Mashup Camp at the Computer History Museum in Mountain View, California (right in the heart of Silicon Valley). At last count, more than 980 photos were loaded into Flickr. Not only do the pictures document some of the content that was generated during the event, they also show the attendees having a great time. Close to 40 distinctly separate discussions were proposed and held during the 2-day unconference.
The sum of the expertise of the people in the audience is greater than the sum of expertise of the people on stage.
What strategy and tools are people using for testing Web Services in CSC? My client is currently starting to build some but has no environment or tools in which to test. The providing application is expecting WS-I Basic Profile-compliant SOAP/XML calls. Some orchestration and performance testing capabilities in the testing environment are desirable.
- You should not attempt migration until after your migration team has studied and learned the .NET environment
- Migration, particularly the first time you do it, is going to be very frustrating
- Migration is in no way a hands-off process
- Some applications simply cannot be migrated automatically
- The only applications worth migrating are those which the company intends to significantly enhance with functionality that only .NET can provide.
In other words, if you've imagined a process by which one loads some VB6 code into the wizard, does a few days' worth of debugging and testing, and emerges with a VB.NET application, you are living a fantasy. And the sooner you abandon that fantasy the better off you will be.
And...
After a developer is sufficiently comfortable with .NET and has spent several weeks in studying the migration process with the tool, Zoufaly says that a migration should progress at an average rate of just 7,000 to 10,000 lines of code per week. Therefore, a 1 million-line VB6 application will take 100 weeks—two years—to upgrade. Seems a little slow for something that Microsoft had the hubris to dub a migration "wizard."
Hmm.
Any way, IT Toolbox has a number of useful looking links here.