How to manage and record a flash meeting?

Question

I call it a flash meeting, but maybe there is another suitable name.

From time to time (and sometimes more often) one of my developers comes to my table and asks how he should encode a certain piece of code.

The code itself does not directly respond to the function, which means that it was not developed during the requirements, but is part of the internal behavior of the function.

After discussion for 5 minutes, we will focus on the solution. My question is: how can I record this discussion so that in the future, when someone else looks at this piece of code, this person will understand why it was designed in this way, and not in this way?

Should I ask the developer to write directly in the discussion summary code or open the Word template and record the discussion, as if it were a 2-hour meeting? Any suggestions?

Answer 1

This is where the development wiki really works. You can simply create a wiki page for a flash meeting and link it to the corresponding other pages. Write down what was discussed, then ask other programmers to check it and update it as you wish. There is one place to write everything, and you can link it to everything you need, for example, SVN refers to a code branch or a link to other wiki pages for other people involved, and work on the code base. Later, if you need to find it, you can also search for keywords that you put on the wiki page to make them easier to find later.

Answer 2

I would do it with code until this essay. a brief paragraph and you're done.

There is nothing that can bother me more than looking at a piece of code and then moving on to some part to search for a Word document that explains this.

So far, his small feature is related to the discussion. large design material should most likely go into your meta-document.

Answer 3

History information may be included in version control validation comments.

In short, information can be captured, then one developer should describe the discussion in a comment when he / she checks the file for version control. If you do not trust the developers to look in the source control, if they have questions, add "View comments for this file on mm / dd / yy" in the comments in the source before checking it.