Daily Productive Sharing 171 - Time for Meetings or Making?

(The English version follows)

#todo #time_management

你厌恶开会吗?你喜欢开会吗?在今天的分享中,作者 Paul Graham 将是否开会作为分割线,将工作模式分为两种:

  1. 管理者模式,日程工作以开会为主,每个会议可能都有不同主题,所以工作的主题也一直会切换;
  2. 创作者模式,日常工作以独自创作为主,不需要开会,可以一直专心在同一主题下工作;
  3. 两者各自相安无事,但是一旦有所交叉就会带来很多问题。比如程序员天然是第二种模式,每天需要独立完成编程任务,必须要十分专注。假如要拉着程序员开会,那么他就无法专心写代码,不仅仅是开会当下无法写,开会后要重启创作者模式也非常困难。
  4. 这也是要一个主管既写代码又做管理那么困难的一个原因吧?

如果你觉得今天分享有帮助,不妨把它分享给你的朋友

原链

Maker's Schedule, Manager's Schedule

Subscribe now

如果你想更好地管理时间,并且减轻自己的压力,不妨试试 BRNR List

如果你也想成为更高效的人,欢迎加入我们的 TG group

如果大家使用邮件订阅,请把 acacess@substack.com 添加为邮箱联系人,避免邮箱过滤的误伤,谢谢:)


Do you loathe meetings? Do you like meetings? In today's sharing, Paul Graham divides the work pattern into two types, using weather having meetings by default as a dividing line.

  1. the manager model, where the work schedule is dominated by meetings, each of which may have a different theme, so the subject of work switches all the time.
  2. the creator mode, where the daily work is based on solitary creation, without meetings, and where work can always be concentrated on the same subject.
  3. the two are each at peace with each other, but when there is some crossover it can cause many problems. For example, the programmer is naturally in the second mode and has to be very focused on his or her daily programming tasks independently. If a programmer is pulled into a meeting, he will not be able to concentrate on writing code, not only in the moment of the meeting, but it will be very difficult to restart the creator mode after the meeting.
  4. This is one of the reasons why it is so difficult for a supervisor to write code and manage at the same time, isn't it?

If you find today's sharing helpful, why not share it with your friends?

Maker's Schedule, Manager's Schedule

Subscribe now

Try our sustainable productivity tool BRNR List

Please add acacess@substack.com as your contact to avoid mislabeling the newsletter as spam.


Excerpt

The manager's schedule is for bosses. It's embodied in the traditional appointment book, with each day cut into one hour intervals.

Most powerful people are on the manager's schedule. It's the schedule of command.

But there's another way of using time that's common among people who make things, like programmers and writers. They generally prefer to use time in units of half a day at least.

For someone on the maker's schedule, having a meeting is like throwing an exception. It doesn't merely cause you to switch from one task to another; it changes the mode in which you work.

Each type of schedule works fine by itself. Problems arise when they meet.