Skip to main content

Coding Stories III - JavaScript and Syntactic sugar

Usually people tend to think that if a code has a low number of lines that it will be more easily to read and understand. A similar ideas is that a code that has a fewer number of lines will be faster.
In this post I will focus only on the first idea – code with a low number of line can be read and understand more easily.
JavaScript sample:
displayCustomValue: function (value) {
        return value !== null ? value === 0 ? "ON" : "OFF" : "";
    }
The cool thing is that it has only one line of code –one and powerful line of code. All of us know what a God class is. Based on this, we could say that our line of code from the method is a God line.
When I looked for the first time over this method I said something like: “Ouuhhh! What is the behavior of this method? … Ahhh, IF value is NULL then return an empty string. ELSE, IF the value is 0 then return ON, ELSE return OFF.
Good, now I understood this line of code. Even if the line looks cool, is not so simple to understand and can generate bugs very easily.
When you need to write something like this, don’t think that writing only one line of code will improve the code in one way or another.
value !== null ? value === 1 ? value === 2 ? "? ": "1" : "2" : "null"
I would retrieve our method to something like this:
displayCustomValue: function (value) {
   if ( value === null )
   {
      return "";
   }
   if ( value === 0)
   }
      return "ON"; 
   }
   return "OFF";
}
Avoid using more than one “? :”  per line in any programming language. Writing code with a lot of “? :” will increase the Ouuhhh factor.

Comments

  1. That's from the same family as obfuscated C++ code: very compact, but easy to understand only by people very familiar with that syntax trick.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP