voluntas I think it is because instantaneous force is judged as excellence programmer. I think that people who have been maintaining the same product for years with continuation are also excellent.
@nishio: Whether itâs considered excellent because it has instantaneous power or inefficiency because it doesnât have continuity is ultimately subjective to the person who perceives it. In the end, itâs just the subjective view of the person who sees it.
@nishio: I donât have the ability to keep going, so I have a technique where I keep a record of what I do on a spur-of-the-moment basis, and then later I have a system that I can refer to and say, âOh, I did this in 2017, and then I did this in 2021. I use a technique to make it a posteriori a continuity by means of a system that allows me to give references to what I did in the blink of an eye. The following is in my 2018 book on this Connecting the Dots
context
@kazuho: I think âgoodnessâ for software engineers is different from âgoodnessâ in a managerial sense. I have the impression that what is important from a managerial point of view is to be able to continuously earn money from a large number of customers through support (including customization).
@voluntas: you are right, it is important to make money continuously. But from a programmerâs point of view, many people donât like to maintain it continuously (they get bored).
@kitar: I donât have much evidence, but I think that programmers who I think âthis person is excellentâ are more likely to be bored. It is a blessing to have such a person close to you and to be able to think of a service that is easy to maintain and easy to make money (easy to earn).
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.