ARTICLES

Articles about software development.

Notes on technical problems, decisions I made, and things I learned while working on projects.

01 Product Design

A Booking Calendar Needs Durations, Not Just Start Times

A 10 a.m. slot is not necessarily free if the previous service is still running. A simple booking calendar depends on durations, working hours, and overlap checks.

Read more
Cover for A Booking Calendar Needs Durations, Not Just Start Times

02 IoT

A Device Alert Is Not the Final Decision

A sensor can detect that a first-aid box was opened. To understand what happened to its contents, the system still needs visual evidence, staff review, and stock records.

Read more
Cover for A Device Alert Is Not the Final Decision

03 Engineering

A QR Code Speeds Up Check-In, but It Is Not the Attendance Record

A QR scan and an attendance record serve different purposes. Keeping them separate makes event check-in easier to review, including repeat scans.

Read more
Cover for A QR Code Speeds Up Check-In, but It Is Not the Attendance Record

04 Operations

Stock Should Not Change When a Request Is Submitted

In an inventory system with layered approvals, a request, a reservation, and a stock movement are three different events. Mixing them makes stock figures hard to trust.

Read more
Cover for Stock Should Not Change When a Request Is Submitted

05 Engineering

Before Building a Dashboard, Fix the Data Flow

A polished dashboard is not much help when the data behind it is late, duplicated, or stuck in an unclear state. I prefer to sort out the data flow first, then decide which numbers and charts deserve a place on the screen.

Read more