C# PROGRAMMING –MAIN DESIGN GOALS

C# is a popular programming language these days, and it was designed from inception to provide a simple, clean, general purpose programming language for those intending to work within the confines of Microsoft’s .NET framework.  Since then, it has been approved as one of the standard languages by both ECMA and ISO, making C# programming an essential tool in every programmers’ kit.

Different languages have different uses and specialties, and C# was designed for programmers to be able to use it to create different components for use in software that would be deployed and distributed en masse, to live use environments.  This means that designers had to really put an emphasis on making the actual source code extremely compatible and portable.  Those already familiar with C or C++ should definitely notice this emphasis.

Another particular point of emphasis during design was focus on internationalization of the language; it was intended from inception to be available all over the world, and to see all sorts of different implementations based on variance in regional programming technique.  The resultant use should help the language develop sophistication as it is refined throughout different versions.

Information Technology (IT) tools are here to support your business in the global market. Effective communication is key for IT and business experts to collaborate effectively in search of solutions. Consulting, reaching out for help to a third-party, can bridge the gap between your business marketing experts and IT operations experts, especially with the emergence of big data analytics and its implication on the global market. Having the right consultants equipped with business knowledge and data technology expertise can make a difference.

Your marketing organization is probably familiar with digital tools and conducting global research. Its results can uncover the journey customers take to purchase your products or use your services. It can highlight the pain points and frictions that prevent their experiences with you to be delightful and amazing. Armed with this knowledge and beautiful compelling presentations, marketing executives expect that IT operations leaders will translate these insights into actions.

But people in IT operations are too involved in meeting key performance indicators that have nothing to do with the end customers. Meeting requirements of faster and cheaper don't translate very well into customer satisfaction. A classic breakdown in communication is described in a Harvard Business Review article, “A Technique to Bridge the Gap Between Marketing and IT.” The author goes on to describe how a new CIO at a bank found IT to be focused on the internal organization as their customers, rather than the real end customer. Moreover, no one was looking at the incident reports which clearly showed that incidents were increasing. And nobody looked at what these incidents were doing to the bank’s customers. The startling and scary numbers of incidents were caught and addressed and brought down from 1,000 to 600 or (40%) and later to 450 per week.

Surprisingly, these type of seemingly isolated scenarios are still being discovered within organizations presently, sometimes internally, and through third party insights such as consultants.  By engaging consultants to provide a perspective based on what they’ve experienced before, they can often bring new and innovative ideas or possible challenges to the table that an internal processes probably wouldn’t have been able to see on their own.  Often, third party input can help to provide the translation needed to go from marketing research results into actions that IT operations can understand and make sense in their high-performance culture. When companies understand and use this knowledge to reassess how to improve their customer experiences, they work backward from what customers want to achieve significantly higher improvements. 

IT and business management are more and more being asked to move away from their traditional roles, such as IT being the "technology infrastructure gatekeeper", and instead become enablers across the enterprise of effective collaboration, big data consumers, and key players in driving desired business outcomes. Marketing leaders look to technology as a way to facilitate the customer's journey and his positive experience of it, bring more clients, and meet increasingly higher loyalty goals. They rely on IT projects to enable big data-based behavioral targeting anywhere in the global market. This means projects to analyze search engine results, improve website personalization and optimization, and building of mobile applications for a more personal experience. All these are projects that consultants with their communication, consulting and technical expertise are well prepared to help in order to bridge the expectation gap between IT and other business organizations.

In order to meet these 21st-century business challenges, Information Technology organizations have been transitioning from waterfall stage-gate project management approaches to agile development. The stage-gate method applies a step-by-step approach where waiting, reviewing and approving are required before moving to the next step in the project. Agile management emphasizes collaboration, no decision hierarchies, and few people roles for making quick, customer-focused small changes over time to deliver solutions that delight and amaze customers. Agile development has allowed many businesses to respond quickly to changing customer desires and expectations. But moving to continuous delivery is a struggle requiring focused, dedicated teams that are not well suited to the traditional matrix organization where people are resources whose time must be "chopped" into many pieces and shared among many projects. Agile teams meet frequently as often as daily but never waiting more than a week to do so.

Marketing people are externally focused. IT people are internally focused. The first works with customer emotions. The second works to increase efficiency. Big data analytic tools are used by the first and supported by the second. Consultants can be the glue that helps both come together in effective collaborations that deliver positive business outcomes in both global and local markets.

Millions of people experienced the frustration and failures of the Obamacare website when it first launched. Because the code for the back end is not open source, the exact technicalities of the initial failings are tricky to determine. Many curious programmers and web designers have had time to examine the open source coding on the front end, however, leading to reasonable conclusions about the nature of the overall difficulties.

Lack of End to End Collaboration
The website was developed with multiple contractors for the front-end and back-end functions. The site also needed to be integrated with insurance companies, IRS servers, Homeland Security servers, and the Department of Veterans Affairs, all of whom had their own legacy systems. The large number of parties involved and the complex nature of the various components naturally complicated the testing and integration of each portion of the project.

The errors displayed, and occasionally the lack thereof, indicated an absence of coordination between the parties developing the separate components. A failed sign up attempt, for instance, often resulted in a page that displayed the header but had no content or failure message. A look at end user requests revealed that the database was unavailable. Clearly, the coding for the front end did not include errors for failures on the back end.

Bloat and the Abundance of Minor Issues
Obviously, numerous bugs were also an issue. The system required users to create passwords that included numbers, for example, but failed to disclose that on the form and in subsequent failure messages, leaving users baffled. In another issue, one of the pages intended to ask users to please wait or call instead, but the message and the phone information were accidentally commented out in the code.

While the front-end design has been cleared of blame for the most serious failures, bloat in the code did contribute to the early difficulties users experienced. The site design was heavy with Javascript and CSS files, and it was peppered with small coding errors that became particularly troublesome when users faced bottlenecks in traffic. Frequent typos throughout the code proved to be an additional embarrassment and were another indication of a troubled development process.

NoSQL Database
The NoSQL database is intended to allow for scalability and flexibility in the architecture of projects that will use it. This made NoSQL a logical choice for the health insurance exchange website. The newness of the technology, however, means personnel with expertise can be elusive. Database-related missteps were more likely the result of a lack of experienced administrators than with the technology itself. The choice of the NoSQL database was thus another complication in the development, but did not itself cause the failures.

Another factor of consequence is that the website was built with both agile and waterfall methodology elements. With agile methods for the front end and the waterfall methodology for the back end, streamlining was naturally going to suffer further difficulties. The disparate contractors, varied methods of software development, and an unrealistically short project time line all contributed to the coding failures of the website.

I will begin our blog on Java Tutorial with an incredibly important aspect of java development:  memory management.  The importance of this topic should not be minimized as an application's performance and footprint size are at stake.

From the outset, the Java Virtual Machine (JVM) manages memory via a mechanism known as Garbage Collection (GC).  The Garbage collector

• Manages the heap memory.   All obects are stored on the heap; therefore, all objects are managed.  The keyword, new, allocates the requisite memory to instantiate an object and places the newly allocated memory on the heap.  This object is marked as live until it is no longer being reference.
• Deallocates or reclaims those objects that are no longer being referened. 
• Traditionally, employs a Mark and Sweep algorithm.  In the mark phase, the collector identifies which objects are still alive.  The sweep phase identifies objects that are no longer alive.
• Deallocates the memory of objects that are not marked as live.
• Is automatically run by the JVM and not explicitely called by the Java developer.  Unlike languages such as C++, the Java developer has no explict control over memory management.
• Does not manage the stack.  Local primitive types and local object references are not managed by the GC.

So if the Java developer has no control over memory management, why even worry about the GC?  It turns out that memory management is an integral part of an application's performance, all things being equal.  The more memory that is required for the application to run, the greater the likelihood that computational efficiency suffers. To that end, the developer has to take into account the amount of memory being allocated when writing code.  This translates into the amount of heap memory being consumed.

Memory is split into two types:  stack and heap.  Stack memory is memory set aside for a thread of execution e.g. a function.  When a function is called, a block of memory is reserved for those variables local to the function, provided that they are either a type of Java primitive or an object reference.  Upon runtime completion of the function call, the reserved memory block is now available for the next thread of execution.  Heap memory, on the otherhand, is dynamically allocated.  That is, there is no set pattern for allocating or deallocating this memory.  Therefore, keeping track or managing this type of memory is a complicated process. In Java, such memory is allocated when instantiating an object:

String s = new String();  // new operator being employed
String m = "A String";    /* object instantiated by the JVM and then being set to a value.  The JVM
calls the new operator */