Why recurring reminders should reset when the work is actually done
That is not always the question a recurring maintenance task needs to answer. Imagine an HVAC filter that should be changed every 90 days. The reminder fires on June 1, but life gets in the way and the filter is actually changed on June 18.
- ▪That is not always the question a recurring maintenance task needs to answer.
- ▪Imagine an HVAC filter that should be changed every 90 days.
- ▪The reminder fires on June 1, but life gets in the way and the filter is actually changed on June 18.
DEV.to (Top) files mainly under programming. We currently carry 4,889 of its stories.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 4047609) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } DataRiver Posted on Jul 26 Why recurring reminders should reset when the work is actually done #flutter #android #productivity #showdev A normal calendar reminder is good at answering one question: what date did I originally choose? That is not always the question a recurring maintenance task needs to answer. Imagine an HVAC filter that should be changed every 90 days. The reminder fires on June 1, but life gets in the way and the filter is actually changed on June 18.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
