Technical News and tips from My learning

The following article is an idea for my research. Abstract Pattern recognition is a branch of Machine learning that focuses on recognition of patterns and regularities in data, although in some cases, it is considered to be nearly synonymous with machine learning. Source: From WikiPedia, http://j.mp/PatRecog This article is an early vision for understanding and recognizing the right algorithm towards identifying the available patterns with the help of parameters that are exposed by the data points of any given situation. 1. Introduction The challenge in this theory is identifying the patterns that are evolving form the enormous amount of data for any given time. Not just that, identifying the right pattern from these possible combinations and executing the analysis with a common methodology. The success of this methodology depends on the algorithm that is used to analyze the available pattern. The crucial situation is to match with the previous data points as well as the...

Now-a-days, I’ve been helping the pre-sales folks towards finalizing the prospective projects for our employer. In the recent time, one of our prospective client asked about the tips to accelerate any project from our experience. I’ve done some investigation and found the following points. I’m documenting here, such that, before I forget them and the effort in identifying these points should not end in vain. Process 1) Expand the team with dedicated developers towards each module – UnitDrivenDevelopment 2) Plan the build delivery 3) DB Management should be ongoing activity 4) Integrating testing as often as possible 5) Prioritize  the Interface Requirement Specifications (IRSs) as frequently as possible Approach 1) Escape the probability approach 2) Avoid problematic functionality 3) Document the Traceability Index 4) Have the reality (nearly real) data with the developers 5) Plan for the asynchronous processing Technology 1) Have the LOGs in place within Code 2) Plan the aud...

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 ...

Most of these days, everyone are moving to cloud apps. More or less, they are deciding to have their applications be available on web. Is it a trend or all requirements are demanding to become web apps? Before we proceed further, from my understanding is that the need of the application decides the nature of the application, neither the investor nor any other party that is involved in the application life cycle. NOT EVEN THE END USER. But how do we understand the nature of the application? The below questionnaire helps in understanding the current requirement. Sl Question Yes/NO/NA 1 Are your users comfortable using a Web browser?   2 Are your users located in remote sites?   3 Do your users in remote sites have access to the Internet?   4 Are you creating a Business to Business (B2B) application?   5 Are you creating a Business to Consumer (B2C) application?   6 Is the amount of data entered minimal?   7 Is the amoun...

While understanding the best practices for exception handling / tracking / etc., in the .NET, I’ve ended up with the below information Best practices in Exception handling within .NET Before identifying the best practices, it is mandatory to identify the exception generation situations and handle them to the best need of the situation. The below is the best scenario for the exception handling.   Fig 1: Exception Workflow [ Source : Internet, I forgot the source link, but I’ve copied this above diagram. As soon I find the source, would mention here. In case if the reader came across of the previous article, please let me know The above diagram is copied from Christian Thilmany ’s blog post from this link . ] There are two ways of handling these exceptions ·          Catch them & Act Immediately o    Early o    Late ·          Catch them to Record (or) log & Act aft...