Engineering notes
Design decisions, Windows integration problems, and the bugs that shipped — written by the person who wrote the bugs.
-
Design decision · 7 August 2026Why DeskDrawer's boards have no title barMost desktop organizers put a title bar on top of each container. Removing it was the first design decision in DeskDrawer, and it drove most of the ones that followed.
-
Windows integration · 7 August 2026Hiding the desktop icon layer without breaking the desktopDeskDrawer has to hide the icons Windows draws, without changing a setting, without surviving a crash, and without upsetting Explorer. Each of those constraints came from a specific failure.
-
Engineering lesson · 7 August 2026The same bug, five times: offline network locationsOne bug class caused every freeze DeskDrawer has ever had. It was fixed in five separate releases before the pattern was fully understood.
-
Engineering lesson · 7 August 2026Three attempts at one check: reparse points, OneDrive and the desktopA one-line safety check took three releases to get right, and two of the attempts caused regressions worse than the problem being fixed.
-
Privacy decision · 7 August 2026Shipping with no telemetry, and what it costsDeskDrawer makes no network connections at all. That is a stronger promise than 'privacy-friendly', and it has a real price the developer pays.
-
Design decision · 7 August 2026Designing an interface that barely needs languageDeskDrawer's Store listing is in 16 languages. The application itself is built so that using it depends very little on reading text in any of them.
-
Development history · 7 August 2026Eight rounds of code audits on a small app, and what each one foundNine of DeskDrawer's releases were stability releases with no new features. This is what eight successive full-codebase reviews actually turned up, including how often a fix caused the next bug.