在我的 todo 文件中，我按日期分组（当我应该处理某件事或完成它时），并在它们前面加上 3-4 个字符的代码来表示“谁”是为了。 例如：
<强>。 等待 。 。 PROD1：查看代码
.MONDAY 。 。 主页：前往银行 。 。 主页：发送账单 。 。 PROD2：编写需求
.TUESDAY 。 。 PROD2：与团队一起回顾
我只计划一周，并在最后保留“稍后”、“稍后”、“我希望”等部分。
I have the same requirements and I have moved from a text file to Google Docs. This gives me a couple of advantages:
I can access it from anywhere
Simple formatting
I have one file called todo and other files for my notes, usually named in a consitent naming convention such as:
product.name.ideas
product.name.todo
product.name.questions
In my todo file, I group by date (when I should work on something or finish it) and prefix them with a 3-4 character code to indicate 'who' is is for. For instance:
. WAITING . . PROD1: Review code
.MONDAY . . HOME: Go to bank . . HOME: Send bills . . PROD2: Write requirements
.TUESDAY . . PROD2: Review with team
I only plan for one week out, and keep sections such as "Later", "Much Later", "I Wish" at the end.
我只是使用 MS Word 作为日志，并在适当的地方插入其他文件的链接。 大多数时候，有了笔记本就足以让我通过阅读最新条目来选择一个项目。
I just use MS Word as a log, and insert links to other files where appropriate. Most of the time, that with a notebook suffice to allow me to pick up a project by reading through the latest entries.
I find a ruled notebook and pen work just fine. I often annotate the margins with icons indicating priority or notes to follow up on later. I think the main thing is to be consistent.
Depends on the project and whether or not the notes are to be shared. I keep my personal notes using pen and paper. Quick and it's easy to add illustrations and references.
Shared notes and FAQ-type tribal knowledge I prefer to use a wiki or development blog for. The blog format is great to provide a timeline and (tagged) references.
I agree with the general consensus so far: keep it simple and focus on your disciplined use. I like using a stand-alone HTML file, since it is plain text but allows real links, various lists, and trivial formatting. This works great for a ToDo list, ReadMe, list of references, ideas, etc.
For an integrated team tool, I prefer a very lightweight wiki. I am targeting Trac (http://trac.edgewall.org/), which is an open-source freeware project that integrates a wiki, source control, and issue tracking--the perfect marriage.
I use TodoList for keeping track during design and actual development. It's a simple hierarchical todo list, but also offers basic project management features (i.e. setting due dates, priorities and categories and tracking progress for tasks). The files are XML and can be easily processed and versioned, and it includes some basic collaboration feature (though I didn't use that so far).
When collecting a large amount of information, especially if it's primarily some text, tables or images, prior to actual development or when brainstorming or just writing down thoughts, I actually use Microsoft OneNote, though I wouldn't install it just for that. But since it's included in Office, which is installed on all computers at my company, I go use it since I'm quite comfortable with it. I use OneNote only for myself, though, as, well, a note book.
Oh, and then, for information that is not really for a single project, but rather to be re-used, we have a Wiki internally, of course, though it's sometimes hard to convince people to actually use that ("what, wiki? I'll just call you when I need that information!"). Sigh.
I usually try to complete a task, before going home. If I'm not able to do it, a good method to remember is to create a failing test for the next thing you should do.
Bigger things I note on the project-wiki or set TODO-comments in my code (and use tools that find them).
发布评论
评论（10）
尝试 Notepad.exe，每个项目一个日志文档。 或者使用Word。 或者维基百科，或者其他什么。
关键不是找花哨的软件，关键是自律，保持日志最新！
try Notepad.exe, one log document per project. Or use Word. Or a wiki, Or whatever.
the key is not to find fancy software, the key is the self-discipline to keep the log up to date!
我有相同的要求，并且我已从文本文件转移到 Google 文档。 这给我带来了几个优点：
我有一个名为 todo 的文件和其他用于我的笔记的文件，通常以一致的命名约定命名，例如：
在我的 todo 文件中，我按日期分组（当我应该处理某件事或完成它时），并在它们前面加上 3-4 个字符的代码来表示“谁”是为了。 例如：
<强>。 等待
。 。 PROD1：查看代码
.MONDAY
。 。 主页：前往银行
。 。 主页：发送账单
。 。 PROD2：编写需求
.TUESDAY
。 。 PROD2：与团队一起回顾
我只计划一周，并在最后保留“稍后”、“稍后”、“我希望”等部分。
I have the same requirements and I have moved from a text file to Google Docs. This gives me a couple of advantages:
I have one file called todo and other files for my notes, usually named in a consitent naming convention such as:
In my todo file, I group by date (when I should work on something or finish it) and prefix them with a 3-4 character code to indicate 'who' is is for. For instance:
. WAITING
. . PROD1: Review code
.MONDAY
. . HOME: Go to bank
. . HOME: Send bills
. . PROD2: Write requirements
.TUESDAY
. . PROD2: Review with team
I only plan for one week out, and keep sections such as "Later", "Much Later", "I Wish" at the end.
我只是使用 MS Word 作为日志，并在适当的地方插入其他文件的链接。 大多数时候，有了笔记本就足以让我通过阅读最新条目来选择一个项目。
I just use MS Word as a log, and insert links to other files where appropriate. Most of the time, that with a notebook suffice to allow me to pick up a project by reading through the latest entries.
我发现直纹笔记本和钢笔效果很好。 我经常用图标来注释页边距，指示优先级或稍后跟进的注释。 我认为最主要的是要保持一致。
I find a ruled notebook and pen work just fine. I often annotate the margins with icons indicating priority or notes to follow up on later. I think the main thing is to be consistent.
取决于项目以及是否要共享笔记。 我用笔和纸记录我的个人笔记。 添加插图和参考文献又快又容易。
共享笔记和常见问题解答类型的部落知识我更喜欢使用维基或开发博客。 博客格式非常适合提供时间线和（标记的）参考资料。
Depends on the project and whether or not the notes are to be shared. I keep my personal notes using pen and paper. Quick and it's easy to add illustrations and references.
Shared notes and FAQ-type tribal knowledge I prefer to use a wiki or development blog for. The blog format is great to provide a timeline and (tagged) references.
我同意迄今为止的普遍共识：保持简单并专注于严格的使用。 我喜欢使用独立的 HTML 文件，因为它是纯文本，但允许真实的链接、各种列表和简单的格式设置。 这对于待办事项列表、自述文件、参考列表、想法等非常有用。
对于集成的团队工具，我更喜欢非常轻量级的 wiki。 我的目标是 Trac (http://trac.edgewall.org/)，它是一个开源项目免费软件项目，集成了 wiki、源代码控制和问题跟踪——完美的结合。
I agree with the general consensus so far: keep it simple and focus on your disciplined use. I like using a stand-alone HTML file, since it is plain text but allows real links, various lists, and trivial formatting. This works great for a ToDo list, ReadMe, list of references, ideas, etc.
For an integrated team tool, I prefer a very lightweight wiki. I am targeting Trac (http://trac.edgewall.org/), which is an open-source freeware project that integrates a wiki, source control, and issue tracking--the perfect marriage.
我使用 TodoList 在设计和实际开发过程中进行跟踪。 它是一个简单的分层待办事项列表，但还提供基本的项目管理功能（即设置截止日期、优先级和类别以及跟踪任务进度）。 这些文件是 XML，可以轻松处理和版本控制，并且包含一些基本的协作功能（尽管到目前为止我还没有使用过）。
当收集大量信息时，尤其是主要是一些文本、表格或图像时，在实际开发之前或进行头脑风暴或只是写下想法时，我实际上使用 Microsoft OneNote，尽管我不会仅仅为此而安装它。 但由于它包含在 Office 中，并且安装在我公司的所有计算机上，所以我会使用它，因为我对它非常满意。 不过，我只将 OneNote 用作自己的笔记本。
哦，然后，对于并非真正针对单个项目而是要重复使用的信息，我们内部有一个 Wiki，当然，尽管有时很难说服人们实际使用它（“什么，wiki？当我需要这些信息时我会打电话给你！”）。 叹。
I use TodoList for keeping track during design and actual development. It's a simple hierarchical todo list, but also offers basic project management features (i.e. setting due dates, priorities and categories and tracking progress for tasks). The files are XML and can be easily processed and versioned, and it includes some basic collaboration feature (though I didn't use that so far).
When collecting a large amount of information, especially if it's primarily some text, tables or images, prior to actual development or when brainstorming or just writing down thoughts, I actually use Microsoft OneNote, though I wouldn't install it just for that. But since it's included in Office, which is installed on all computers at my company, I go use it since I'm quite comfortable with it. I use OneNote only for myself, though, as, well, a note book.
Oh, and then, for information that is not really for a single project, but rather to be re-used, we have a Wiki internally, of course, though it's sometimes hard to convince people to actually use that ("what, wiki? I'll just call you when I need that information!"). Sigh.
我通常会在回家之前尝试完成一项任务。 如果我做不到，记住的一个好方法是为你应该做的下一件事创建一个失败的测试。
我在项目维基上记下的更重要的事情或在我的代码中设置 TODO 注释（并使用找到它们的工具）。
I usually try to complete a task, before going home. If I'm not able to do it, a good method to remember is to create a failing test for the next thing you should do.
Bigger things I note on the project-wiki or set TODO-comments in my code (and use tools that find them).
我使用 TiddlyWiki，这是一个有用的个人 wiki。 我使用它就像一大盒记事卡，各部分之间有交叉链接和超链接。
正如一些人提到的，这些系统中最困难的部分是保持最新。
I use TiddlyWiki, which is a useful personal wiki. I use it like a big box of notecards, with crosslinks and hyperlinks between sections.
As several people have mentioned, the toughest part of any of these systems is keeping it up to date.
如果您需要共享信息，Wiki 非常适合您想要记住的“部落知识”类型的信息。
如果只是为了你自己，那么这里给出的其他答案非常有效。
If you need to share the information, a Wiki works really well for this "tribal knowledge" type information you are looking to remember.
If it's just for yourself, then the other answers given here work really well.