程序员在学习新学科或技术时更喜欢使用什么方法
当你学习一门新学科或新技术时，你用什么方式来记住你的成就？
过去，我使用过多种方法，包括以下一些方法：-
- 纸质日记本（用断头台将 A4 纸切成两半，并用塑料书脊装订。） 我按时间顺序保存，并经常重新排列页面以将连续页面或类似页面分组在一起。
- 电子邮件 - 我经常通过电子邮件将代码片段发送给自己
- 测试程序 - 简短的独立项目代码片段。
- ProtoPage.com - 基于网络的笔记存储库。
- 记忆——通常是最不可靠的方法，但有时它更好。
最后：-
- 堆栈溢出 - 我之前在研究解决方案时在这里问过一个问题。然后回来提供我自己的答案。这是堆栈溢出的可接受用途吗？当我想到问题时就提出问题，然后一个小时、几个小时或几天后当我解决完问题后回来提供答案。也许同时回来看看我得到了什么答案，也许为我提供新的尝试方向。
我很想创建一个博客，在那里我可以存储我所有这些类型的发现之旅，但我认为把它放在这里可能会有更大的价值。
请各位女孩和男孩们提出想法、意见和方法。
When you are learning a new subject or technology what ways do you use to remember your achievements ?
In the past I have used a variety of methods including some of the following :-
- Paper-based Journal (A4 paper cut in half with a guillotine, and bound with a plastic spine.) I keep this chronologically, and frequently reorder the pages to group continuations or similar pages together.
- Emails - I frequently email snippets of code to myself
- Test programs - Short self-contained snippets of project code.
- ProtoPage.com - web based repository of notes.
- Memory - frequently the least reliable method, but occasionally it's better.
Finally :-
- Stack overflow - I previously asked a question on here as I was working on the solution. Then came back to provide my own answer. Is this an acceptable use of Stack overflow ? Banging in questions as I think of them, and then coming back to provide an answer an hour, few hours, or maybe days later whn I've worked through it. Maybe coming back in the meantime to see what answers I'm getting, maybe providing me with new directions to try.
I was tempted to create a blog where I can store all these kinds of voyages of discovery I have but I think there may be greater value putting it on here.
Thoughts, opinions, and your methodologies girls and guys please.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果您为所有应用程序构建一个核心库，您可以将其用于参考/注释等。您不需要记住代码的完整实现，您只需要记住对其所在位置的引用（这自然/结构上类别通过你的代码）
If you build a core library for all your applications, you can use that for reference/commenting etc. You dont need to remember the full implementation of code, you just need to rememeber a reference to where it is (which is naturally/structurally categories by your code)
问题是博客正是实现您想要的目标的手段。它是一个在线参考，允许协作，当你整天在 SO 上发布“随机”问题并在一周内找到答案时回答它们时，你不会被打成碎片。
SO 基本上是问答，而博客是您的问题和编码问题的解决方案的运行计数器。
它也没有坏处，可以从您的博客中获得一些不错的认可，并为自己在社区中赢得一些声誉/追随者。
The thing is a Blog is exactly the means to achieve what you are wanting to. Its an online reference, allows for collaboration and you won't get shot to pieces when you post "random" questions on SO all day long, and answer them in a week when you find the answers.
SO is basically Q&A whereas a blog is a running counter of your problems and solutions to your coding problems.
It doesn't hurt either, can get some nice recognition from your blog, and gain yourself some reputation/followers in a community.