Technical interviews as I noticed are different from regular interviews. More so with Web Development and specifically frontend technical interviews.
And because of that, it is very important to understand what is required for a interviewee beyond the obvious technical skills to succeed in the interview.
In this post, I will try to cover some of the points that might be useful for interviewees to consider keeping in mind for technical interviews.
As much as you are well versed technically for the candidature, if you are not good at the small behavioral traits that panelists specifically look at, it will be a challenge to impress them in the best possible way. …
Hi there, how are you doing.
This post can be considered as a written version of my YouTube mini-series on image upload end-to-end functionality.
All the code shown here is available in this Github repo.
The intention of this post and the corresponding YouTube playlist on image upload functionality is this:
There are not many good tutorials on how to upload an image in a neat way. I thought it would be great to have a demo that includes this.
Hey there, how are you doing.
All the code that I explain here is available in this Github repo.
Here is what MDN says:
The Window.history read-only property returns a reference to the History object, which provides an interface for manipulating the browser session history (pages visited in the tab or frame that the current page is loaded in).
Every time you click on a link in a web-page or a hashtag within the page, a history entry gets recorded in the browser session.
Essentially, history.pushState method on the history object can be used to create and activate a new history entry manually. There is another method called history.replaceState, which actually replaces the immediate last entry into the history of the browser session. Using both these methods, we can associate arbitrary data to the history entries that they create and access that data when the user goes to that particular entry point at a later time. …