Technical News and tips from My learning

This post is not about any technical concept, but about the concepts of a given team (or) the comparison of traditional and agile teams Traditional Teams Parameter SelfManaged Teams Direction and Control Manager's Role Coaching, facilitation, and support Manager Responsibility for Performance Team Top Down Information Flow Downwards, upwards and cross Narrow, single-task roles Job Role/Function Whole process and multiple task Top Down, imposed Decision Making By Team, within agreed boundaries Manager Authority Team   Static Development of team Evolutionary   This above table is taken from a magazine that is currently not in print. Executive Capsule is the name of the magazine.

This post might seems funny, writing about COM in the time of Cloud. Yet, this is a long time pending notes that I’ve prepared and are not documented. This is the time that I felt to document, of course, there are much information that is available on web. This would be an extra page that define the COM Architecture. I see the need of this architecture in 4 directions. # INTEROPERABILITY Components must be compatible with the 1) application’s environment where they are used 2) and also with the components developed by the 3rd party vendors # VERSIONING Components must NOT require upgrades, if applications containing them are upgraded # TOOL INDEPENDENCE Components must PERMIT development tool interoperability, while create any development tool (or) language during design time # DISTRIBUTED FUNCTIONALITY Components must have an ABILITY to generate components that support not only function in process but also across process and networks ie., DOM   Final NOTE: COM is not ...