一般开发说明
在典型的日常编程中，我以我想要记住的方式实现函数。 例如，假设我调整了一个数据库插入功能，当我再次遇到这种情况时，我想找到我做了什么来重新使用。 我需要一个地方来保存解决方案（我所做的），并且我需要以某种方式找到它，这可能是几个月或一年后。 使用思维导图的想法，我正在考虑建立一个个人维基，但后来我听到 stackoverflow 播客提到使用这个网站是出于这样的原因。 有没有其他人记录他们所做过的巧妙的事情，以便他们将来某个时候可以找到它。 如果是的话，您使用了什么，一般来说，您如何使用它？
我喜欢个人博客想法并使用堆栈。 我将尝试在堆栈上发布然后自己回答的想法，这有利于其他人可能提出他们的意见。 只要堆栈会存在一段时间:)
During a typical day programming, I implement functions in a way that I would like to remember. For instance, say I tuned a DB insert function that, when I come across the situation again, I want to find what I did to resuse.
I need a place to keep the solution(what I did), and I need to find it somehow, which may be months or a year later. Using a mind map sort of idea, I was thinking about a personal wiki, but then I heard the stackoverflow podcast mention using this site for such a reason. Does anybody else keep track of slick things they've done so that they may find it sometime in the future. If so, what did you use, and in general, how do you use it?
i like to personal blog idea and using the stack for it. i'll try the idea of posting at the stack and then answering it myself, with the benefit of other people potentially giving their opinion.
As long a the stack will be around for a while :)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（13）
Jeff Atwood 建议使用 Stack Overflow 来处理此类事情。 发布问题（您的问题），然后发布答案（您找到的解决方案）。 这可以让您与世界分享信息，并可能获得一些有价值的反馈或更好的解决方案。
（哇，我因为重复杰夫·阿特伍德的话而被否决了。我保证我不会再这样做了。）
Jeff Atwood recommends using Stack Overflow for this kind of thing. Post a question (your problem) and then post an answer (the solution you found). This lets you share the information with the world, and maybe get some valuable feedback or better solutions.
(Wow, I got downvoted for repeating what Jeff Atwood said. I won't do that again, I promise.)
我一直使用 neomem 。 我给自己写笔记。 然后我以后就可以搜索它。
I use neomem all the time. I write notes to myself. Then I can later search for it.
您可能会发现这些问题很有用
You may find these questions useful
我使用个人 Wiki、我的 del.icio.us 书签和我自己的博客。 通常我的博客：当我学到一些我知道我可能会再次偶然发现的东西时，我会在我的博客中写一篇简短的文章。
I use a personal Wiki, my del.icio.us bookmarks and my own blog for that. Usually my blog: When I learn something that I know I might stumble on again I write a short post in my blog.
我使用 WikiDPad 或 Wiki-On-A-Stick。 它不仅适用于代码片段，还可以做笔记、记录遇到的典型问题以及如何解决这些问题和文档。 相信我的话，如果你有适当的笔记，它会让你的工作变得更加容易......并添加相互链接的力量，你就拥有了杀手级资源。 我的记忆力很差，记笔记使我的表现提高了一个数量级。 它还可以让您不必向别人询问同一个问题两次或三次。 另外，如果有人问同样的问题，您可以帮助他们访问 wiki，他们可以阅读并在需要时添加内容。
I use WikiDPad or Wiki-On-A-Stick. It works not only for code snippets but also to take notes, record typical problems you get and how to solve them and documentation. Take my word for it, it makes your job a LOT more easier if you have proper notes... and add the power of interlinking to it and you have a killer resource. I have very bad memory and taking notes has improved my performance by an order of magnitude. It also saves you from having to ask someone the same question twice or thrice. Also, if anyone asks the same question, you can just helpfully point them to the wiki and they can read it and add to it if they need to.
您所想到的技术术语是“代码片段”，通过谷歌搜索您会发现许多程序旨在为各种平台存储它们，包括完全基于网络的程序，例如 这个。
The technical term for what you are thinking of is "code snippets", and googling for that will find you many programs designed to store them for a variety of platforms, including entirely web-based ones such as this one.
我在工作的服务器上设置了 dekiwiki，我和我的同事用它来处理公司特定的内容，同时也用于处理出现的一般编程技巧。
I set up dekiwiki on a server at work that my coworkers and I use for company specifics stuff but also for general programming tips that arise as well.
一个简单的维基百科可能会有用。 请参阅Tiki 维基
A simple wiki, may be useful. SeeTiki Wiki
我总是把它放在我的博客上。 我不仅可以稍后再回顾它，而且还有机会帮助其他人。
I always put it on my blog. Not only am I able to get back to it later, there is also a chance that it can help someone else as well.
这是老式的，但我在笔记本上记笔记。 使记住解决方案（或导致解决方案的问题）变得更容易。 通常我每天做1-2页笔记。
与此类似的数字化形式是保留私人博客或日记。 添加搜索程序来帮助您查找内容很容易。
我的老板可能感兴趣的有价值的事情，比如错误和用户调用，都会被输入到错误跟踪软件中，并在那里得到更正式的处理。
It's oldschool, but I keep notes in a notebook. Makes remembering solutions (or the problems that caused them) a bit easier. Usually I make 1-2 pages of notes a day.
The digital equivalent of this would be keeping a private blog or journal. Easy enough to add a search program to help you find stuff.
Worthwhile things that my boss might be interested in, like bugs and user calls all get entered into bug tracking software where it is more formally handled.
我在我的个人项目中使用了优秀的 Trac 项目管理系统，并且我使用它的 wiki 作为集思广益和注释- 获取工具。 而且，因为它还连接到 Subversion 存储库和错误跟踪系统，所以我可以从我的笔记直接链接到特定的代码部分或错误报告。
I use the excellent Trac project management system for my personal projects, and I use it's wiki as a brainstorming and note-taking tool. And, because it also hooks into the Subversion repository and the bug tracking system, I can link from my notes right to a particular section of code or a bug report.
我将我的个人项目保存在 assembla 上。 Wiki、问题跟踪、源代码控制...非常有用。
I keep my personal projects on assembla. Wiki, Issue Tracking, Source Control... very useful.
检查您的编辑器是否具有某种注释功能。 理想情况下，您可以将代码中的特定位置与小注释链接起来，并将其存储在集中位置。 如果没有，这种插件构建起来不会太难，你最大的障碍将是如何将一段代码链接到一个文件（由于代码的易失性），甚至那个插件也不是并不是不可克服的。
Check to see if your editor has some kind of annotations feature. Ideally you could link a particular location in code with a small note, and store it in a centralized place. If it doesn't, that kind of plugin wouldn't be too hard to build, your biggest hurdle is going to be how to link the piece of code to a file (due to the volatile nature of code) and even that one isn't insurmountable.