---
title: "Comment by Praneet Brar on \"Null Is Not Zero: Building an Honest \"Time Back\" Estimator in React With localStorage\" | Hashnode"
description: "I like how you keep the raw input as a string and use null for “not entered”; it stops a blank field from quietly becoming a fake zero. The note that overlappin"
url: "https://hashnode.com/posts/null-is-not-zero-building-an-honest-time-back-estimator-in-react-with-localstorage/6afc2ba55bae59c0d6dd1883/comment/6afc4ae996c3ae41d26908e4"
---

[Discussion](https://hashnode.com/posts/null-is-not-zero-building-an-honest-time-back-estimator-in-react-with-localstorage/6afc2ba55bae59c0d6dd1883)

Comment [Null Is Not Zero: Building an Honest "Time Back" Estimator in React With localStorage](https://hashnode.com/posts/null-is-not-zero-building-an-honest-time-back-estimator-in-react-with-localstorage/6afc2ba55bae59c0d6dd1883)

[Praneet Brar](https://hashnode.com/@praneetbrar)

[2h ago](https://hashnode.com/posts/null-is-not-zero-building-an-honest-time-back-estimator-in-react-with-localstorage/6afc2ba55bae59c0d6dd1883/comment/6afc4ae996c3ae41d26908e4)

I like how you keep the raw input as a string and use null for “not entered”; it stops a blank field from quietly becoming a fake zero. The note that overlapping habits aren’t counted also makes the estimate’s limits clear. How did you settle on the “time back with people” wording?
