在越野跑时完成四项开发任务
我发现自己在不坐在电脑前的时候，往往能想到最好的创意。
我之前的工作流程是：
- 外出
- 想到一个创意
- 在手机上记下来
- 希望能记得稍后查看（这很少发生）
但现在我的流程是：
- 外出
- 想到一个创意
- 启动编码/创意/研究助手来执行我想到的事情
- 回家后进行审查
既然可以直接开始做事情，何必还要记下来呢？
所以今天我决定进行一次测试，看看在跑步的时候能完成多少开发工作。
我的工作流程：
启动一个初始任务，走上小径，每当到达阴凉的地方，就查看任务，合并那些通过测试的任务，并根据需要开始新的任务。
最终结果：
- 跑了大约5英里，穿过博伊西的山脚
- 海拔上升约550英尺
- 启动了7个开发任务
- 审查并合并了4个拉取请求
在跑步时启动、开发并合并的开发任务：
- https://github.com/scottfalconer/compact-memory/pull/399
- https://github.com/scottfalconer/compact-memory/pull/400
- https://github.com/scottfalconer/compact-memory/pull/401
- https://github.com/scottfalconer/compact-memory/pull/402
Strava地图：
- https://strava.app.link/e83SL3bz2Tb
查看原文
I tend to tend to get my best ideas when I'm not sitting in front of a computer.<p>My general workflow was:<p>- Be out.
- Think of idea.
- Make a note on my phone.
- Hopefully remember to look at it later. (Rarely happened)<p>but now it's:<p>- Be out.
- Think of idea.
- Kick off coding / creative / research agent to do whatever I’m thinking of.
- Review when I’m home.<p>Why make a note when you can just as easily start doing the thing?<p>So today I put it to the test and decided to see how much dev work I could get done while on a run.<p>My workflow:
Kick off an initial task, head out on the trails, whenever I got to a shady spot, check the tasks, merge the ones with passing tests, and start new tasks as needed.<p>End results:<p>~5 miles through the Boise foothills.
~550ft elevation gain.
- 7 development tasks kicked off.
- 4 pull requests reviewed and merged.<p>Development tasks initiated, developed, and merged while on the run:<p>https://github.com/scottfalconer/compact-memory/pull/399
https://github.com/scottfalconer/compact-memory/pull/400
https://github.com/scottfalconer/compact-memory/pull/401
https://github.com/scottfalconer/compact-memory/pull/402<p>Strava map:<p>https://strava.app.link/e83SL3bz2Tb