Technology Blog

Look deep into latest news and innovations happening in the Tech industry with our highly informational blog.

The most useful Frontend coding tips and Database concepts


Frontend development is very important these days. There are a lot of tasks that a frontend developer has to do on a daily basis.

As front-end developers, we write a lot of HTML, CSS, and JavaScript code all the time. Knowing some coding tips could be very beneficial for us. That’s why in this article, I decided to share with you some frontend coding tips that you probably don’t know.

Hiding an HTML element

Do you know that you can hide an HTML element without using JavaScript?

By using the attribute hidden, you can easily hide an HTML element natively. As a result, that element won’t be displayed on the web page.

Here is the code example:

<p hidden>This paragraph won't show up. It's hidden by HTML.</p>

Use the inset shorthand in CSS

It’s always a good practice to use shorthands in order to make your CSS code smaller. The property inset in CSS is a useful shorthand for the four properties top , left , right , and bottom .

If these four properties have the same value, you can just use the property inset instead and your code will look much cleaner.

Here is an example:

Bad practice:

  position: absolute;
  top: 0;
  left: 0;
  bottom: 0;
  right: 0;

Good practice:

  position: absolute;
  inset: 0;

Detect internet speed

You can easily detect internet speed in JavaScript by using the navigator object. It’s very simple.

Here is an example:


Pic courtesy:

As you can see above, it gives me 5.65 since my internet speed is not good at all.

Vibrate your phone

Again, you can easily use the method vibrate()in the navigator object to vibrate your phone.

Here is an example:

//vibrating the device for 500 milliseconds


So as you can see, the device in this situation will vibrate for 500 milliseconds.

Disable pull to refresh

By using only CSS, you can disable pull to refresh on mobile. The property overscroll-behavior-y allows us to do that. Just give it the value contain .

Here is the example:

 overscroll-behavior-y: contain;

Prevent the user from pasting text

There will be situations where you will need to prevent the user from pasting text into inputs.

Well, you can easily do that in JavaScript using a paste event listener.

Here is an example:

<input type="text"></input>
//selecting the input.
  const input = document.querySelector('input');
//prevent the user to paste text by using the paste eventListener.
  input.addEventListener("paste", function(e){

As a result, now users can’t paste the copied text into the input field.

Database Concepts

Databases are the backbone of our applications, and the more you learn about how they work, the better you will be at using them, writing applications against them, and troubleshooting problems when things inevitably go wrong.
So let’s dive into seven things you should (probably) know about databases.

Choosing the Right Database Is Hard

We’ve seen a lot of dogmatic fist-banging about “the best” or “the worst” database, but the truth is the best database is the one that works best for your application. There’s no one-size-fits-all sort of database just like there’s no one-size-fits-all programming language or operating system.

When starting a new project, choosing the right database can be one of the most crucial decisions that you’ll make. So how should you choose which DB to use? We put together a list of five things to consider in our article on databases for developers, but let us also quickly go through them here.

What kind of data will be stored in the database?

Are you storing log files or user accounts?

How complex is the data that will be stored?

Can the data be normalized easily?

How uniform is the data?

Does your data roughly follow the same schema or is it disparate or heavily nested?

How often will it need to be read or written?

Is your application read- or write-heavy, or both?

Are there environmental or business considerations?

Do we have existing agreements with vendors? Do I need vendor support?

By answering these questions, you can help narrow down your choices to a few candidates. Once there, testing should tell you which one is the best for your application.

Moving to the Right Database Is Harder

Sometimes you don’t have a choice and the database is already chosen for you. Whether you came to the project after it was started or political winds forced you a certain way, using the wrong database for the job can be frustrating.

But equally, if not more, frustrating is the progress of migrating databases should you get the opportunity. Once you start down one path, it’s not easy to simply change paths in the middle of things. Not only do you have to figure out a way to replicate your data from one database to another and learn a whole new system, but depending on how tightly coupled your database code is with the rest of your application, you might also be looking at extensive rewrites as well. Changing databases is not a task that should be undertaken lightly and without a lot of consideration, debate, testing, and planning. There are so many ways that things can go horribly wrong. This is why #2 is so important: Once you choose, it’s hard to undo that choice.

NoSQL Doesn’t Replace SQL, It Complements It

The debate about using a SQL or NoSQL database will go on forever. We get that. But often missed in this argument is the fact that NoSQL databases don’t replace SQL databases. They complement them.

There are some things that NoSQL databases do very well and there are some things that SQL databases do very well. Prometheus is very good at storing time-series data like metrics, but you wouldn’t want to use MySQL for that. Is it technically possible? Yes, but it’s not designed for that and you’re not going to get the best performance or developer experience out of it. On the flip side, you wouldn’t want to use Redis to store highly relational data like user accounts or financial transactions for the same reasons. Sure, you could make it work in the code, but why add that complexity and headache when you could just use the right tool for the job?

There is going to be some inevitable overlap in some areas. There are some excellent databases that are technically NoSQL that do a good job of storing relational data (see: Couchbase), but there are other outside factors that go into using one over the other. Factors like client language support, operational tooling, cloud support, and others are all things to take into account when choosing a database.

For more information and to develop web applications using modern front-end technology, Hire Front-End Developer from us as we give you a high-quality solution by utilizing all the latest tools and advanced technology. E-mail us any clock at – or Skype us: “hkinfosoft“.

To develop your custom web app using JavaScript, please visit our technology page.

Content Source: