I try to build features that users can actually finish with.While building a logistics management web flow and mobile label-printing features, I learned that a working button on the screen is not enough. Reservation intake, Excel upload, label printing, mobile permissions, device selection, and output results all had to connect before the workflow could be used in actual operations. Since then, I try to check the user order and likely blocking points before building a feature.

I try to write code where state and data flow are visible.While building several business screens with React and TypeScript, I saw how quickly small changes become hard to predict when reads, writes, and screen state are mixed together. I used TanStack Query to organize server-data refresh flows and Zustand to separate screen state such as modals and tables, with maintainability in mind.

I narrow unfamiliar problems down under real conditions.When connecting a mobile WebView to Android native modules for Bluetooth printer output, browser-side debugging alone was not enough. I narrowed down causes by checking Android permissions, the WebView bridge, device SDK behavior, and label data formats on real devices. In the Posture Teacher project, I also improved a performance issue by moving from an OpenCV-based implementation to MediaPipe.