Daily Productive Sharing 306 - How to Work Smarter?

Daily Productive Sharing 306 - How to Work Smarter?
Photo by Icons8 Team / Unsplash

One helpful tip per day:)

(下附中文版)

#todo #time_management

Tim Ferries wrote the bestselling book "The Four-Hour Work Week" and, not coincidentally, Patrick McKenzie only spends five hours a week on his personal projects, and today's post is a summary of his experience. This article is particularly detailed, and some of it has been very helpful to me:

  1. time is an asset; time is a debt: make time your asset rather than a debt, i.e., make money while lying down as much as possible.
  2. code only accounts for 10% of your business, maybe less: many programmers start businesses to write code, not to solve business problems.
  3. cut scope ruthlessly: do everything possible to focus
  4. wall clock time VS calendar time: calendar time refers to the need to be time-tested, such as AB test must collect a certain period of data to see the problem; and wall clock time refers to the tasks we can plan in a short time, we have to optimize the wall clock time as much as possible, do not let the wall clock time to wait for the calendar time.

If you enjoy today's sharing, why not subscribe?

Running A Software Business On 5 Hours A Week

Need a superb CV, please try our CV Consultation


Tim Ferries 曾经写过一本大火的畅销书《每周工作四小时》;无独有偶,Patrick McKenzie 说他在自己的个人项目上每周只花五小时,今天的分享来自他的经验总结。这篇文章特别细致,其中有些对我的帮助非常大:

  1. 时间是资产;时间是债务:要让时间变成你的资产而不是债务,也就是尽可能躺着也要赚钱;
  2. 代码只占你业务的10%,也许更少:很多程序员为了写代码而创业,而不是为了解决商业问题而创业;
  3. 无情地削减范围:尽一切可能聚焦;
  4. 挂钟时间 VS日历时间:日历时间指的是需要经过时间检验的,比如 AB test 必须收集一定周期的数据才能看到问题;而挂钟时间是指我们可以短时间内规划的任务,我们要尽可能地优化挂钟时间,不要让挂钟时间去等日历时间。

This post is for paying subscribers only

Subscribe to DPS - Daily Productivity Sharing

Sign up now to get access to the library of members-only issues.
Jamie Larson
Subscribe