from The Intellectual Production of Engineers Reaction Summary
Importance of trial and error and recommendations for sharing
Engineers.試行錯誤の過程を共有し、透明性を持って行動する重要性についてのツイートのまとめ。特に、この過程を公開することや新しい技術の取り組みにおいて初期の「試行錯誤フェーズ」を設けることが強調されている。
- https://twitter.com/satoru_takeuchi/status/1034487329065295872
- I completely agree with the expression “Trial and error is hard to see…” in “The Engineer’s Art of Intellectual Production.”
- When you teach people things, it’s easy to tell them the answer or the solution, but it’s hard to tell them the trial and error of finding it.
- It’s many times longer than just saying the answer.
- If you’re used to it, you can skip a lot of things, but not for the person you’re teaching.
- I’ll have to leave the results of my trial and error and how it went, for example, in a commit message.
- https://twitter.com/mhiramat/status/1034577487110397952
- Because of this, when you are doing trial and error on OSS (with the aim of eventually committing), you should not do it alone, but raise the issue in ML or issue first trial and error in a visible place.
- And not only trial and error, but quality improvement is equally invisible. It is still a good idea to do it in the open.
- That’s the part you don’t see in the git log.
- I can do a reverse lookup if the issue# is attached. lkml has a URL attached these days, so I can do a reverse lookup from http://lkml.org, but the trap is that I have to attach a link to the previous series in the cover email to get to it.
- That’s the part you don’t see in the git log.
- https://twitter.com/yoosee/status/1034951720617426944
- I try to create a “trial and error phase” at the beginning of a project where I have discretion, especially when using new frameworks, middleware, or packaged software.
- As a rule, anything made for trial during that period is discarded.
- Until you learn the etiquette, copying of a sutra or trial and error is necessary.
- In reality, there are many projects in which I have no discretion, so I’m not always on the cutting edge, but if I do something new without clear trial and error, the design or implementation that I initially created by misunderstanding something will become a very big liability later on.
- When you teach people things, it’s easy to tell them the answer or the solution, but it’s hard to tell them the trial and error of finding it.
- I completely agree with the expression “Trial and error is hard to see…” in “The Engineer’s Art of Intellectual Production.”
Trying something new without trial and error is a huge liability.
This page is auto-translated from /nishio/試行錯誤の重要性と共有のすすめ 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.