General development notes

Question

During typical daytime programming, I implement functions in a way that I would like to remember. For example, let's say I set up the database insert function, which, when I encounter a situation again, I want to find what I did to resume work. I need a place to save the solution (what I did), and I need to find it in some way, which could be months or a year later. Using an idea like a mind map, I thought about a personal wiki, but then I heard a mention of the stackoverflow podcast that uses this site for this reason. Does anyone else keep track of the slippery things they did so they can find it sometime in the future. If so, what did you use, and in general, how do you use it?

---

I like the personal idea of ​​the blog and the use of the stack for it. I will try the idea of ​​placing on the stack, and then I will answer it myself, to the benefit of other people who can give their opinion. As long as the stack is around for a while :)

Answer 1

Jeff Atwood recommends using qaru for this kind of thing. Ask a question (your problem), and then send an answer (found solution). This allows you to share information with the world and possibly receive valuable feedback or the best solutions.

(Wow, I got an offer for repeating what Jeff Atwood said. I won’t do it, I promise.)

Answer 2

I use neomem all the time. I write notes to myself. Then I can find him.

Answer 3

You may find these questions helpful.

• Where do you store code snippets?
• Useful Information Tracking
• Which site do you prefer for code snippets?

Answer 4

To do this, I use the personal Wiki, my del.icio.us bookmarks and my own blog. Usually my blog: When I find out something that, as I know, can stumble again, I write a short entry on my blog.

Answer 5

I use WikiDPad or Wiki-On-A-Stick. It works not only for code snippets, but also for taking notes, recording typical problems that you get, and also for solving them and documentation. Take my word for it, it makes your work easier if you have the right notes ... and add the power of interconnection with it, and you have a killer resource. I have a very bad memory, and notes improved my work by an order of magnitude. It also eliminates the need to ask someone the same question twice or thrice. Also, if someone asks the same question, you can just point them to the wiki and they can read it and add to it if they need to.

Answer 6

The technical term for what you think is “code snippets,” and a Google search for you will find many programs designed to store them on different platforms, including fully web versions such as this one .

Answer 7

I installed dekiwiki on the server at work, which my colleagues and I use for the specifics of the company, but also for the general programming hints that also arise.

Answer 8

A simple wiki can be useful. See Tiki Wiki

Answer 9

I always put it on the blog . Not only can I return to him later, there is also a chance that he can help someone else.

Answer 10

This is oldschool, but I'm taking notes in a notebook. Makes memorizing solutions (or the problems that caused them) a little easier. I usually take 1-2 pages of notes per day.

The digital equivalent of this would be keeping a private blog or magazine. It's easy enough to add a search program to help you find material.

Useful things that my boss might be interested in, such as bugs and user calls, all fit into bug tracking software, where he is more formally processed.

Answer 11

I use Trac's excellent project management system for my personal projects, and I use it as a tool for brainstorming and taking notes. And since it also connects to the Subversion repository and bug tracking system, I can link to my notes directly to a specific section of code or an error report.

Answer 12

I keep my personal projects in the assembly. Wiki, problem tracking, source control ... very useful.

Answer 13

Check if your editor has some kind of annotation feature. Ideally, you could associate a specific place in the code with a small note and store it in a centralized place. If this does not happen, such a plugin will not be too complicated to build, the biggest obstacle will be how to connect a piece of code with a file (due to code variability), and even that, 'insurmountable.