In a part-time business known as BitMap Productions, Chaitanya Marvici became dedicated to producing high quality, user friendly, and maintenance friendly solutions for our customers and clients. We have also worked together as developers for a single client in a full-time capacity, and were seen as being the 'backbone' of the development and maintenance efforts for a complex, long-term project. BitMap Productions later became Marvici Enterprises to reflect the wider range of services that we provide.
It is well known among employers and managers, that there are no two people who are exactly alike. Often times, development teams are weakened by hiring personnel who ignore or are unaware of this fact, and hire personnel to fill a specific need instead of hiring personnel who are able to both fill and support the needs of the group. When building a strong development team, one must acknowledge and construct a team in a way that each developer can augment the others and strengthen the group as a whole.
In the past, development efforts were divided into three definitive groups: mainframe, client/server and desktop. However, with the rise of the popularity of the Internet and Intranets, the advantages of real-time interconnectivity between all systems within an organization, has become a requirement instead of just a dream or wish. At first, the only solution was for an organization to hire a developer to build bulky, proprietary, job-specific systems software solutions to bridge the gap. This type of development was able to bridge the gap, but rarely did it do so in a real-time manner. Furthermore, its proprietary nature meant that it was only suitable for organizations that were not expected to grow, or were capable of providing for large in-house development groups.
A few companies, both large and small, set out to build middle-ware packages that would help developers to build and maintain real-time systems to the required platforms. Some were geared toward the mainframe-to-client/server bridging efforts, and others toward the client/server-to-desktop (or remote client) efforts. Often times, these packages carried a high-dollar price tag, and did not stand to reduce the overall cost of an environment, but instead, expanded the personnel and equipment requirements to support the packages.
With the release of the .NET framework in the second quarter of 2002, Microsoft presented the first low-cost solution to the problem of interconnectivity. The .NET framework seemed to simplify development efforts, and allow those efforts to be developed by existing web development personnel. Yet, as with just about any product, there are hazards and dangers associated with the framework that could stand to slow or stall development efforts from time to time. The majority of the hazards, center around the fact that the .NET framework is currently a Microsoft solution and thus geared toward the use of Microsoft components such as their browser, web servers, etc. Some of the more prominent dangers, come from the assumption that the .NET framework contains a sort of new 'intelligence' that will allow one coding methodology to cover all aspects of development. This assumption is going to be the reason that two identical systems have such differing development timelines, resource consumption levels, and overall levels of success.
As two pieces of the same development team, this is where our combined experiences of client/server, desktop, intranet, Internet and third-party packages can serve to greatly strengthen the development efforts of an organization. Individually, Our past experiences include that of large, interactive client/server systems, as well as efforts to solve browser and client interaction differences -- together -- in one simplified effort. We share many similar web application areas of expertise which have proven to complement each other toward a solid solution.