Code Quality & Performance Virtual Conference

In this session I will be talking about OpenSource ( Git & GitHub ) from basic to advance concepts of Git & GitHub. We will be discussing about how we can gain more experience in writing code through Git & GitHub and also will talk about how we can excel our Code Quality with Git & GitHub.

This session is focused on optimizing performance that involves more than just implementing efficient code. The user’s experience of application performance must also be considered.

There are many techniques for increasing the performance and perceived performance, of Xamarin.Forms applications. Collectively these techniques can greatly reduce the amount of work being performed by a CPU, and the amount of memory consumed by an application.

Profile & Monitor Web Application with Azure Application Insights: In the session, the below will be discussed

1. Introduction to Application Insights

2. Understand App Insight’s features for tracing Performance issues

3. Understand the architecture of how App Insights fits in a Web Application along with other Azure Components

4. Learn Distributed Tracing of the Application with end-to-end co-relation of the various Components

5. How Application Map provides performance metrics of Individual Components

6. Learn how to Enable Profiling for Windows and Linux apps hosted in Platform as a Service

7. Enable the Profiler, Simulate traffic, troubleshoot the app performance and identify the exact line of the code that’s causing the performance bottlenecks

Bob Kemper, VP of Worldwide Engineering at OverOps, will explore four BIG challenges facing financial services software applications: MTTI and MTTR, Avoiding Downtime, Speed and Stability, and Distributed and Partner/External workforce challenges.

The financial services industry has undergone massive disruption in recent years. Now, more than ever, financial institutions need to out-pace the competition in delivering simple, feature-rich and secure digital experiences. But at the crux of these digital transformation initiatives is the speed-stability paradox. Innovation cannot come at the cost of reliability; especially when the financial services industry has to consider governance, security and privacy.

In the financial services industry, the customer experience needs to be seamless. When it comes to the movement of money, any lag or misstep that could lead the user to question the status and safety of their money, even for a moment, can instantaneously erode trust and irreparably impact brand reputation and the bottom line.

As more financial services organizations accelerate release velocity as part of their competitive strategy, they are encountering a myriad of software reliability issues – often in mission-critical applications – leading to catastrophic, headline-making outages. This speed-stability conflict is made even more challenging by the pressures of financial industry regulation and compliance that dictate every move. Every move they make is closely scrutinized, and even a single unexpected error can expose the integrity of customer transactions and lead to massive fines and other regulatory consequences.

Top 10 Tips of Architecting Secure-First Software:  Software and data security and privacy must be the top priority when architecting a new software system. There are over 1 million new cyber-attacks each days almost every company is a victim of data hacks and cyber attacks. It is software architects and developers, who should think security of data, APIs, and UI from the day 1. In this session, Mahesh will share his top 10 (or more) tips on what you can do to build secure software systems that are bullet proof any hacks.  

I will briefly go through the testing pyramid and tell about unit, integration, automaton testing approaches for .NET web applications with some code examples.

Cloud Microservices to Serve the Next Billion: The food wastage in India is 70 tons per year, and there is mismanagement at several layers. Approximately 20-30% of the wastage happens in the last mile, between wholesale traders, and retail mom-and-pop stores. Is there something we can do about food wastage?

This was the problem statement I attempted to solve as a first engineering hire at a startup. Our customers were 12.8 million retail owners that deal in FMCG (Fast-moving consumer goods, such as food grains, tooth paste, etc.). The goal was to develop a platform for retail traders (mom and pop shop owners / small and medium business owners) to buy FMCG products from wholesale traders using an Android app.

We were attacking a deeply entrenched business practice to help solve a societal goal. For a section of the population which is not very well versed with smartphones and technology, the user experience had to be designed from the ground up to be multilingual, fungible, unstructured, and relevant. In this talk, I cover how we went about iterating the solution from a simple SMS based system to a full fledged app backed by microservices. Having a micro-service architecture provided us the agility to experiment and iterate quickly, and we were able to push out changes much faster, and help solve wastage problems even sooner.

I will discuss the several problems we faced in this segment with regards to unstructured data, and how our data models had to adapt. We used a bunch of cloud native services such as DynamoDB, Redshift, Kinesis, Lambdas, etc. to develop this marketplace, and I will discuss how these services came together in a cogent form.

After having worked in bigger companies on software projects that scale to millions of devices, this was a unique challenge for me, and something I am very proud of. I would like to share my experience in building empathetic software for the masses.

Performance is at the heart of .NET, with an incredible amount of energy invested in every release towards making the stack faster and more scalable. In this talk, Stephen Toub will walk through example changes that have improved performance in the .NET stack over time, highlighting how such changes benefited apps and services running on .NET, and how those changes can serve as a blueprint for further improvements in your own code bases.

We all want to have someone else review our C# code to make sure it’s written well. Wouldn’t it be even better if we can have that review process done automatically? In this session, you’ll see how you can use static analysis tools to find all kinds of implementation issues before they show up in a release. You’ll also see how you can create your own analyzers to hunt down problematics areas in code.

Five people working together at one computer?!  How can that possibly be productive? While this is a reasonable question, it’s not easily answered – until we begin to understand the power of flow.

Mob Programming grew from one team’s quest  to learn how to work well together. Once we started working as a true team we almost immediately noticed that working this way provided better results in a variety of ways:

1. We were getting more done, and they were the more important things

2. The quality of our work was increasing dramatically

3. Our knowledge, skills, and capabilities were improving rapidly

4. And all while we were having a lot of fun!

I have said to engineers until I am blue in the face that management, for the most part, does not care about code quality or code/ application performance. They just want to “ship it” and get their bonuses! They do not care about unit testing and so much more, so it is up to you to push it for your team. But you, being the developer, will be left holding the bag if something goes wrong, not management that could lead to you losing your job. Even worse, when major changes must be made that causes you to a lot of re-writing of the code, management will get upset that it is taking so long. Therefore, proper architecture standards are so important. I will discuss what every app that goes into production must at a minimum have:

1. Architecture

2. Coding Standards

3. Unit Testing and More Unit Testing

4. Continuous Integration

5. Application Testing

6. Proper Environments

7. Memory Profiling

These 7 subjects are key to launching a new app or system that customers will love and keep using!