Lighthouse is an open-source, automated tool that can be run on any web page (public accessible or requiring authentication) to improve the quality of that page. It can conduct audits for performance, accessibility, progressive web apps, SEO, and more on a web page.
We are living in extraordinary times. With the onset of the COVID-19 pandemic, the state of the world has changed.
Everything we considered “normal” has shifted, and for the most part, everyone’s life has been disrupted and turned upside down.
During these times of change, it can be difficult to cope, especially when trying to balance so many elements of your life such as work, family life, and social needs.
For the most part, these elements may have been separate in your life before this situation or were easier to segregate from each other. …
Flutter toast notification messages are an essential part of an app. They are used to provide feedback to a user. Similar to a tooltip or a popup, they only remain on screen for a few seconds.
In this blog, we are going to share how to build such notification messages in 5 simple steps. More specifically, we are going to build reusable toast messages using alert dialogs, as shown in the image below:
Firstly, let us customize an alert dialog to appear as a toast message.
By using the showGeneralDialog method in Flutter, we can show an Alert Popup. …
We all are aware of how time-consuming the process of translation can be. What if there was a solution to reduce the extra effort needed when developing a product in multiple languages and make internationalization easier?
In Angular, such a solution exists — in the form of a module — that can be leveraged when developing an application to be used in multiple languages or locales.
Internationalization can be defined as the process of developing a software application in multiple languages without making any code changes. Internationalization is usually used with localization. …
At DLT Labs we use several distributed ledger technologies, but the one that probably gets the most focus is Hyperledger Fabric.
We build enterprise-strength products. In my two years developing on that platform, I’ve encountered some unique challenges relating to the scale and additional requirements of large-scale systems.
We thought we would share one such situation in which we decided to introduce a clustered state database for our Fabric peers and to show interested developers how that was done.
The product was already using Apache CouchDB as its state database in Fabric so that a variety of other components could query the ledger directly and enjoy a richer querying experience. We wanted high availability of the database to those other components, and to ensure that the load generated by them did not impact the availability of the peer. …
In our coding journey, we strive for perfection. During this eternal journey, we may face situations where there is a need to optimize our written code. This endeavor may result in lengthy and bulky lines of code.
Opting for useful libraries such as Lodash to optimize code seems like a good option in such instances. We follow advanced terminology (like for e.g. external libraries) to avoid writing complex lines of code, comprising of many validations, loops, and if-else conditions.
Lodash provides many useful functions for arrays, collection, object, string, Math, Number, Lang, Date, etc.
High quality code with good style is not only essential for a developer, but also makes it easier to maintain the software. If you make stable software with good style, then your system will be able to demonstrate high performance.
If programmers use an organized way for writing source code, it will improve source code readability and understandability, and conform to a standard style. This can help avoid introducing errors in the code.
In this blog, we are going to share a few conventions for naming and ordering packages, classes, methods and variables which are in line with best practices.
Let us discuss naming, ordering, and formatting code. Before getting into the particulars, it is a good practice to write code in such a way that it should be self-explanatory. …
Impact Analysis is the methodology to study the requirements’ data, to understand the pros and cons of any change. As the world keeps evolving, changes are to be expected, even in a well-developed system.
Changes can happen for a variety of reasons: a change in a client’s requirements, adjustments to business needs or new technologies.
Since changes can potentially result in a failure, it is prudent to proceed with proper planning when making necessary changes.
This is where “Impact Analysis” comes in.
This is a technique that helps to identify the consequences of any changes being planned in a software or a product. …
An important aspect of creating and maintaining your production environment is performing health checks.
These are useful to ensure flawless business continuity, and make it easier to be vigilant, acting as early warning systems. These systems monitor and trigger alerts at the right time, giving us the time needed to come up with solutions and react appropriately.
In the modern era of microservices, most of the industry has moved to docker based deployments for its production environment. This enables teams to provide the horizontal scaling needed, among numerous other advantages, as compared to traditional deployment methods.
But what makes Docker based APIs so useful here, especially in situations where a service or an application needs no port to run? …
Client credentials flow in OAuth 2.0 is generally used for authenticating the service rather than the user. This grant_flow is used for machine to machine communication.
In this grant flow, the client registers itself with the OAuth 2.0 compliant authorization server. In return, the OAuth 2.0 compliant authorization server provides it with client_id and client_secret.
Here are a few concepts to remember if you are new to this topic: