Conversation Log 2020-06-08

- What exactly does [[crunch task]] mean?
- Check for documentation first.
- Then [[Word frequency in source code]] analysis
- Create a document that will serve as a guide.
- Read and understand the source code and write tests
- Refactoring
- Add functionality
- [[Documents to guide you]] makes it easier to get back to the project if you forget what it is.
- Makes it easier for people who don't know what the project is about to participate
- It has to do with the recent "One person's project should become a multi-person project".
- Documentation is needed to involve others

• As the project progresses from the stage of coming up with the idea to the specifics, the documentation becomes more specific. - Similar to what I wrote in [Prototypes and Proposals

Let’s talk. What would you like to see happen in this conversation? What exactly is a chewing task? Is there anything else about that chewing task? Bite into ideas and turn them into actionable actions. Is there anything else about that action? How can we learn to understand this when we are in a state of not understanding it? Is there anything else you can tell us about that condition? It’s been a while since I’ve been away from the project, so I think I’m forgetting a lot of things. Is there anything else you can tell us about that project? Not much documentation left on the project. What type of project is it? A project that was left unattended after being shaped to a certain degree Where is the project located? It’s in a repository somewhere. Is there anything else about that repository? I should write a document, and maybe I’ll write one.

Projects that were left unattended after being shaped to some degree Where is this project located? NG What type of document is it? Ideally, the internal structure of the project should be described, so that when you read it, you know what to tweak when making new improvements. How do you know about the project? If there is documentation, you can read it, but there isn’t. Is there anything else about that document? I guess I’ll just have to make it now while reading the source code. What type of source code is that source code? I think it has a bizarre shape because I made it while experimenting with various things. Is there anything else you can tell us about its shape? Maybe refactoring would be a good idea. If there is documentation, you can read it, but there isn’t. How do you know about this document? I heard the other day that it would be good to run a word frequency analysis on the source code and generate a model from that. Is there anything else about that source code? I need to see if there is documentation first and read the source code to see if I can chew it up into concrete actions. Where is that document located? I don’t know if it’s there or not, so I check, that’s the first task. Is there anything else about that task? If not, the next task is to apply word frequency analysis to the source code What type of task is the task? It’s the task of creating a rough model of the source code. How do you know its source code? Read it, understand the features, and then you can test code the features you understand for future refactoring. Is there anything else about that refactoring? Should be done separately from feature additions. Refactoring should come first. I think there was a saying that expressed this… What type of refactoring is that refactoring? To make the tangled code into a clean structure without changing the behavior of the code, so that you don’t have to worry about it when you do a new modification. Is there anything else you can tell us about its structure? Keep it simple. It’s the task of creating a rough model of the source code. Where can I find this source code? NG

I'll have to check to see if there is documentation first, and read the source code to see if I can chew it up into concrete actions.

What does this document look like? Map. A rough guide that points you where to go. What is it that you value? A guide will lower the cost of deciding on a Next Action. This is value. What type of guide is that? A guide that shows you where and how to fix things without having to re-read and re-understand the entire source code Is there anything else you can tell us about that guide? Like a table of contents for a book. What is the relationship between the project and the source code? This living system, in which the source code is properly updated, will continue to grow like a snake that repeatedly sheds its skin, and this living system is the project Is the project the same as the source code? Is it different? To use an analogy, is a human being the same as a body? It’s like saying that a dead person has the same body as a living person. What happens to the source code when a project UPDATED. What happens to a project when it is in source code? New ideas, user reactions, needs, and other growth opportunities are created by moving the source code. What is the connection between that source code and the project? Putting that aside, “What exactly do I need to do about the chewing task?” As for the “chewing task,” I’d say first check for documentation, then do a word frequency analysis of the source code, create documentation to serve as a guide, read and understand the source code, write tests, refactor, add features, and so on. What is the relationship between that guide and the project? Documentation that makes it easier for people who don’t know or have forgotten what the project is about to participate in the project. Ah, well, it has to do with the “one person’s project should be a multi-person project” from the other day. What is the relationship between the project and its documentation? Documentation is needed to get others involved, he said. Is the document the same as the project? Is it different? In a sense, is documentation more important than source code for a project to continue? What happens to the document when that project is done? As the project progresses from the stage of coming up with the idea to the specifics, the documentation becomes more specific. What happens to the project at the time of that document? So, the documentation will support the project to keep it alive. What does that project look like? lifelike What is the connection between the project and the documentation? bye-bye

---

This page is auto-translated from /nishio/会話ログ2020-06-08 using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I’m very happy to spread my thought to non-Japanese readers.