How I manage my KDE email
The author shares their email management routine in KDE, treating emails as tasks for inbox zero. They use Thunderbird or KMail, categorize emails, address urgencies promptly, and suggest unsubscribing for efficiency.
Read original article
The article discusses the author's email management routine within the KDE environment. The author treats emails as tasks assigned to them, aiming for inbox zero to indicate completion of tasks. They separate KDE and non-KDE emails, use an email client like Thunderbird or KMail, and employ automatic and manual categorization methods. Urgent emails are promptly addressed, while merge request and bug report emails are managed efficiently. The author emphasizes deleting emails after action, considering them as tasks rather than historical records. They suggest unsubscribing from unnecessary email sources to reduce the email load and maintain a manageable inbox. The article provides insights into the author's workflow and offers tips for effective email management, encouraging a proactive approach to handling emails to enhance productivity.
Related
Avoiding Emacs Bankruptcy
Avoid "Emacs bankruptcy" by choosing efficient packages, deleting unnecessary configurations, and focusing on Emacs's core benefits. Prioritize power-to-weight ratio to prevent slowdowns and maintenance issues. Regularly reassess for a streamlined setup.
My (Neo)Vim workflow
An experienced Vim user shares tips on optimizing the (Neo)Vim experience through Personalized Development Environment (PDE), covering search techniques, keybindings, plugins, movement enhancements, text manipulation, quickfix list, spell check, and status line customization.
My .gitconfig File Dissected
The article delves into .gitconfig file breakdown, covering user details, GPG key signing, Git aliases, and workflow optimization tips. Encourages readers to customize their .gitconfig for enhanced Git usage.
A dev's thoughts on developer productivity (2022)
The article delves into developer productivity, emphasizing understanding code creation, "developer hertz" for iteration frequency, flow state impact, team dynamics, and scaling challenges. It advocates for nuanced productivity approaches valuing creativity.
Your Company's Problem is Hiding in Plain Sight - High Work-In-Progress (WIP)
The article explores the negative effects of high Work-In-Progress (WIP) in software development, drawing parallels to a WWII story. It highlights signs of high WIP and advocates for a balance between productivity and rest.
0 commentsRelated
Avoiding Emacs Bankruptcy
Avoid "Emacs bankruptcy" by choosing efficient packages, deleting unnecessary configurations, and focusing on Emacs's core benefits. Prioritize power-to-weight ratio to prevent slowdowns and maintenance issues. Regularly reassess for a streamlined setup.
My (Neo)Vim workflow
An experienced Vim user shares tips on optimizing the (Neo)Vim experience through Personalized Development Environment (PDE), covering search techniques, keybindings, plugins, movement enhancements, text manipulation, quickfix list, spell check, and status line customization.
My .gitconfig File Dissected
The article delves into .gitconfig file breakdown, covering user details, GPG key signing, Git aliases, and workflow optimization tips. Encourages readers to customize their .gitconfig for enhanced Git usage.
A dev's thoughts on developer productivity (2022)
The article delves into developer productivity, emphasizing understanding code creation, "developer hertz" for iteration frequency, flow state impact, team dynamics, and scaling challenges. It advocates for nuanced productivity approaches valuing creativity.
Your Company's Problem is Hiding in Plain Sight - High Work-In-Progress (WIP)
The article explores the negative effects of high Work-In-Progress (WIP) in software development, drawing parallels to a WWII story. It highlights signs of high WIP and advocates for a balance between productivity and rest.