Sometimes you need to keep values stored locally, for example:

• to prevent data loss due to network failures.
• to keep unfinished editing for a long time (example, this editor)
• to exchange data between different pages without sending it to the server(implementing a shopping cart)

When designing beautiful web pages we have the tendency to fallback to the well know options. This most of the time reduces to Bootstrap and Material Design. If you want to offer flexibility in your design proposal is important to know what other frameworks in the market can offer to you.
I’ll be listing the different design frameworks I’m finding in the wild with notes on the pros and cons I find in them. If you want to keep updated with the list just subscribe.

Believes about mistakes can prevent teams from working at full speed. Your culture about mistakes makes the difference between being a top performing and someone from the heap. So, knowing how to approach mistakes in the most productive way and building a culture around that is a skill that will make the difference.

This video is kind of a map to the services we can find in amazon AWS.

A list of 50 PM terms that helps quickly refer to how to manage a project.

Here you will can find some references to secure coding practices and how to test for security

Also important to create a sitemap.xml file

Use case, we want to know how much time an element has been visible. For example, an ad before refresh.

Adding an extra level of security is increasingly important to avoid our data from being stolen. Using two factor authentication is a simple yet effective way to accomplish this goal.

Properly hashing is difficult. Some popular hashing algorithms have been probed vulnerable (MD5)
So, here are a couple of options that allow to hash in a cryptographically safe way.

Requiring a schema to validate JSON data is a common task.
Usually, you start by simply sending the data to the service. As more data is added, one day dealing with data complexity turns out to be difficult.
So, validating that the data is as expected turns out mandatory.
The simplest way to come up with a first schema to be used for validation is to generate it based on json data.
In this post I present two tools that helps pull off this task very easly.

Commands frequently used in git for branch management.

The web-vitals library is a tiny (~1K), modular library for measuring all the Web Vitals metrics on real users, in a way that accurately matches how they’re measured by Chrome and reported to other Google tools (e.g. Chrome User Experience Report, Page Speed Insights, Search Console’s Speed Report).

The library supports all of the Core Web Vitals as well as all of the other Web Vitals that can be measured in the field:

UI Frameworks like bootstrap, material design, tailwindcss come with a lot of CSS helper classes to enable you with flexibility in the design of which you end up using only a small fraction. At the time of creating the production file you end up with big files that slow down your pages loading and degrade the user experience.
Getting rid of all css classes that are not used is a simple way to optimize your pages performance.

Creating your own npm libraries is useful if you want to smoothly share your code between projects.

Keeping your javascripts light is something pressured by UX requirements. Pages with big javascripts tend to load slowly, on the other hand for a provider is difficult to know in advance what tools to include because they are known only when the script is run.

Sometimes you need to implement a download link in a web page.

Having unique ids is a frequent need. Sometimes using a database can help on this but at the cost of speed. Here are a few faster alternatives.

Mindsets are a set of believes that you acquire during your life that shortcut your decision making. They are based on stories, cultural approach to problems and are shortcuts to the complexity we find in life. They help us in arriving to conclusions quickly and to make decisions effortless but some of them limit our possibilities. Identifying those mindsets allow us to increase our chances of success.

Adding backlinks to a website helps in allowing people to find it on the web.
There are tools that helps you out to add them and to verify how many already exists.

Technical debt are decisions we make during development that we know are not optimal because they require more work to get optimal but we decide to deal with the consequences because we see more value in delivering at that time.

Free api is an option.

Different ways of implementing Core Web Vitals

Heroku dyno filesystems are ephemeral, non-persistant and not shared between dynos. So when you do heroku run bash, you actually get a new dyno with a fresh deployment of you app without any of the changes made to ephemeral filesystems in other dynos. So, to be able to manage files on web using Heroku you have to resort to other solutions. See a couple in the note details…