Urgent.News

What's breaking now, across thousands of outlets.

Tech

Honest talk: motivation is unreliable, so I stopped depending on it

Some days I'm excited to code. Some days I'd rather scroll. If my output depended on mood, I'd ship very little. This post is about building a routine that works on both kinds of day. It isn't a productivity sermon, and it isn't a promise that discipline fixes everything. It's a handful of practical mechanisms, plus an honest note about the limits. The core idea: don't negotiate with your mood…

This article explores how motivation fluctuates and the benefits of building routines that work regardless of mood. The writer shares several practical methods they use to maintain productivity and consistency.

To avoid relying on motivation, the writer recommends defining the smallest possible task the night before, so starting the work requires minimal decision-making. Using a timer for short focused sessions of 25 minutes can also help, as stopping after the timer ends creates momentum. Removing distractions by ensuring the editor and terminal are ready, and putting the phone in another room, makes the path to starting the task easier.

Instead of focusing on hours spent working, the writer suggests counting the number of non-zero days, with a baseline minimum task required each day to keep the streak going. This approach emphasizes consistency over intensity. Guilt is noted as an ineffective motivator, as it increases the unpleasantness of starting, leading to avoidance.

The writer cautions against burnout, acknowledging that doing less on low-energy days is acceptable. They encourage taking breaks when necessary, such as when sleep patterns are poor, the work feels unfulfilling, or personal life is overwhelming. Rest is essential for maintaining overall well-being and preventing deeper issues.

A weekly reflection includes checking what was actually completed, what drained energy, and identifying a small change to make the upcoming week easier. The writer stresses that these guidelines are general principles, not personalized advice. They recommend experimenting with one change for two weeks to see its impact on individual habits.

The article concludes with a sample weekly routine, emphasizing flexibility and customization to fit individual lifestyles. Simple rituals, such as reading the previous day's task and setting a timer, can help kickstart the day. Tracking the number of days the minimum task is accomplished provides motivation without obsessing over hours logged. Ultimately, taking a break is a healthy option when personal well-being is compromised, and returning with a smaller scope can help maintain productivity.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

CI/CD for Monorepos 2026: Build Only What Changed

TL;DR: A monorepo with naive CI rebuilds the world on every commit, so pipelines get slower exactly as the repo succeeds.

  • Naive CI rebuilds entire codebase on every commit, causing slowdown
  • Affected-only delivery detects changes, expands through dependency graph
  • Start with path filters in GitHub Actions, graduate to build tools like Nx

SMS OTP Resend in Node.js: Message IDs, Backoff, and Delivery Errors

Short answer: treat an OTP resend as a state transition on the original SMS message, not as a fresh “send again” button. Keep the message ID from the first send, call the resend operation with that…

  • Retain original message ID for SMS OTP resend in Node.js
  • Implement state transitions (pending, accepted, failed) based on response
  • Limit resend attempts to prevent uncontrolled code streams

More from Saturday 31 October →