Urgent.News

What's breaking now, across hundreds of outlets.

Tech

How to stop forgetting to reply to messages (habits + WhatsApp and Gmail settings)

You read it. You thought, "I'll answer properly later." Three days later the person writes again – "Did you see my message?" – and you feel terrible. Forgetting to reply is one of the most common small failures of modern life, and it isn't a character flaw. It's a design problem: opening a message marks it as read, and "read" looks like "done". Here's how to fix it, with habits that work on any…

The article discusses strategies to combat the habit of forgetting to reply to messages. It suggests using the "two-minute rule", where a reply is given if it takes less than two minutes or the message is marked for later. For longer responses, a brief holding reply acknowledging receipt and providing a specific time to answer is recommended.

Batch processing of replies during set times throughout the day can help manage this task more effectively. Templates and voice messages can also be used to expedite the response process. Additional features such as message reminders, snoozing emails, and star/label systems can aid in keeping track of pending replies. The article also advises addressing any late replies promptly and maintaining a structured approach to avoid repetition of mistakes.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

structuredClone vs JSON.stringify: I Timed Both on Node 22

On Node 22, JSON.parse(JSON.stringify()) cloned objects 1.6 to 1.75 times faster than structuredClone across three sizes structuredClone handles Dates, Maps and circular references that the JSON…

  • JSON.stringify is significantly faster than structuredClone in Node 22
  • structuredClone loses data types like functions and undefined values
  • Benchmark results confirm speed gap is real and not script-specific

Debugging Without Guessing: A Practical Method for Finding the Real Problem

Every developer eventually runs into a bug that seems to make no sense. The page is blank, even though the component looks fine. A function works with one input and fails with another.

  • Clearly define the bug with specific expected and actual outcomes
  • Reproduce the issue consistently to gather reliable evidence
  • Analyze error messages for clues about the bug's origin

Offcall is a desktop app for the two minutes after an incident

This is a submission for the Presage SmartSpectra SDK Challenge What I Built Offcall is a desktop app for the two minutes after an incident, before the handoff note gets written.

  • Offcall is a desktop app for on-call engineers during critical incidents.
  • Uses Presage SmartSpectra SDK to read user's breathing rate.
  • Provides sequential questions: what happened, what's open, what's down.

More from Saturday 21 November →