Debugging on Commentary of Takao

Recovering Deleted Branches and Commits using git reflog

Sat, 25 Apr 2026 00:00:00 +0900

“I accidentally deleted a local branch using git branch -D,” or “I ran git reset --hard HEAD~1 and lost my unpushed commits!” If you have worked with Git for any length of time, you have likely experienced one of these stomach-dropping moments.

While standard git log commands won’t display references to deleted branches or detached commits, you don’t need to panic. Git has a built-in safety net called git reflog.

Robust Frontend Exception Management with Error Boundaries

Tue, 20 Jan 2026 00:00:00 +0900

Why Error Boundaries Matter

In React applications, a single uncaught JavaScript error in a component can crash the entire UI. Before Error Boundaries, this meant users would see a white screen with no indication of what went wrong. Error Boundaries are React components that catch JavaScript errors anywhere in their child component tree and render a fallback UI instead of crashing.

Implementing an Error Boundary

Error Boundaries are class components that implement one or both of the static lifecycle methods getDerivedStateFromError and componentDidCatch:

Finding Regression Commits Quickly using git bisect

Mon, 20 Oct 2025 00:00:00 +0900

“It worked yesterday, but it is broken today.” In any active software project, regression bugs are bound to slip in. Finding the exact commit that introduced a bug out of hundreds or thousands of commits can feel like searching for a needle in a haystack.

Instead of manually checking out commits one by one or spending hours analyzing code changes, you can use Git’s built-in debugging tool: git bisect.

In this article, we’ll explain how to use the binary search algorithm of git bisect to locate the origin of a bug in minutes.