deep-work-prioritizer
Advanced tools
An organizational tool for ranking your weekly priorities around the concept of 'deep work'
A simple personal CLI dialogue that can be used for ranking weekly work priorities around the concept of 'deep work' vs. 'shallow work'. It attemps to give an estimate of the actual time that can be allocated for doing your weekly deep and shallow work based on common time factors like meetings, short-weeks, etc.
👉 By providing the number of scheduled meeting hours and number of days you're working this week, your actual availability for deep & shallow work can be calculated.
👉 All priorities identified as deep work are evenly split across 75% of the actual working hours you've allotted this week.
👉 All priorities identified as shallow work are evenly split across 25% of the actual working hours you've allotted this week.
Install via $npm install -g deep-work-prioritizer, then run the command: deep-work.
FAQs
An organizational tool for ranking your weekly priorities around the concept of 'deep work'
The npm package deep-work-prioritizer receives a total of 4 weekly downloads. As such, deep-work-prioritizer popularity was classified as not popular.
We found that deep-work-prioritizer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
