Abhinav Sharma induratized

Frontend Technical Interview Prep

EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.

I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.

Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.

Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca

Debugging in a React app with a sea of console.log statements can be a nightmare. To keep logs manageable, you can create a simple log wrapper utility that only logs messages from certain files or folders, and is easy to enable/disable when needed.

✅ Quick, Flexible Solution: Custom `logger.js` Wrapper

Step 1: Create `logger.js`

// utils/logger.js

Good commit messages serve at least three important purposes:

To speed up the reviewing process.
To find out what changed in a range of commits (e.g. for a release note).
To help the future maintainers, say five years into the future, to find out why a particular change was made to the code or why a specific feature was added.

Structure your commit message like this:

🚨 If You Already Popped or Dropped the Stash

If you've already run git stash pop or deleted the stash, you can try to recover it from reflog:

git reflog

Look for a line like:

Thanks for the update. If git stash apply didn’t restore your staged changes, it’s very likely that:

🧠 Your staged changes are in the stash, but not restored by default

When you run:

git stash apply

To stash only unstaged + untracked files, while keeping staged changes intact, you can use:

git stash push --include-untracked --keep-index

✅ Explanation:

--keep-index: Leaves your staged files untouched.
--include-untracked: Includes untracked files (e.g. new files you've created but haven't added to Git yet) in the stash.

Ah — now I understand the nuance in your question. You're using Vite's native index.html handling, and yes:

✅ In Vite's default behavior:

When you run:

npm run build

🧾 Git Worktree Workflow — Best Practices and Automation

✅ Why Use `git worktree` in a Monorepo?

Work on multiple branches without switching or stashing.
Avoids dirty working directory issues.
Ideal for parallel development, review, testing, and fixes.
Keeps main worktree clean and focused.

Here are all available "rsp-ui.rsp.*" settings you can use in your VS Code User or Workspace settings.json, as provided by the Runtime Server Protocol UI extension ([marketplace.visualstudio.com][1]):

⚙️ General Extension Flags

rsp-ui.rsp.java.home Specifies the path to a JDK (11+) to launch the RSP server and default Java-based runtimes. ‣ Example:

	[
	"",
	"A.B. High School",
	"A.G. High School",
	"A.G.High School, Dapoli",
	"A.G.JAIN HIGHER SECONDARY SCHOOL",
	"A.R.S.D College",
	"A.S.S. College",
	"A2Z Computers",
	"Abhinav Inseva Sansthan Mahavidyala",