tweet2021-04-23
nishio: I was thinking of writing a lot of feedback this year, but I'd rather not even bother to write feedback, like a review memo that's one line "not specific". I'm not sure if I should be thinking about how to improve the proposals that I do >>Proposal Enhancement nishio: First of all, the proposer is submitting the proposal because he/she does not foresee that such a decision will be made, but this can be done rather easily by self-determination. The first question to ask is, "If this project is accepted, what will you do first thing tomorrow?" You can ask yourself if you can answer the question, "If this project is accepted, what will you do first thing tomorrow? This is a question that we also ask those who pass the screening process. nishio: The reason I ask this question is because if I can't answer it, it means I can't do anything unless I tell you what to do, and I Basically, I don't tell them what to do, so it is not a project. This is probably why the term "self-propulsion" is used. I don't pull people who don't move on their own. nishio: So far, I've dropped people from the application screening process because they were "not specific enough". I guess it is necessary to think about what is necessary for such people to be able to run on their own. I guess the first thing I need to do is to Google what I'm proposing and find something similar. nishio: Most ideas are similar. If you find something similar, find out how it works. If you find a word you don't understand, look it up too. If you keep repeating this, you will either understand how it works, or you will realize that the mountain you were trying to climb is much higher than you expected. nishio: If you know how it works, you will know the Next Action. If you realize that the mountain is too big, the next action would be "how to make it smaller". For example, even if you cannot do 100% of what you want to do with existing tools, try to do as much as you can first. Then, "the rest" is the problem to be solved. ukkaripon: sometimes you're applying because you want advice on what to do next, maybe. nishio: If that's the case, then the system should be improved because resources are being wasted on both sides due to mismatched intentions. For example, provide easier documentation and create a contact point where people can ask "what should I do next?". nishio: If this story is about the application process to satisfy the desire to know what the next action is, then it is fundamentally wrong, and you should take knowledge acquisition actions to at least find out the next action before applying. If you don't know how to do it, or if you don't know how to do it, then the mechanism is not well designed. nishio: next story. The pattern of thinking about what you want to make, then researching similar things, and then finding an existing tool that seems to do what you want to do, but you're just applying for it. This is also, well, "let's use it" first. When you use it, you'll see the pros and cons. nishio: this is another of those "resolution is increased by comparing it to something similar" types of things. ---
This page is auto-translated from /nishio/tweet2021-04-23 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.