The object of understanding is ambiguous.

• Decoupling "Understanding" from "Results" The definition of "understanding" is ambiguous with respect to
• Divide it into "understanding the syntax of the programming language" and "understanding the needs of the user".
• The delay in "making something that works and showing it to the user" by insisting on understanding the former is an obstacle to understanding the latter.
  • There are trade-offs between multiple understandings.
• Until now, it has been Highly necessary to understand the syntax of the programming language in order to create a prototype at a level that can be shown to the user in order to obtain "an understanding of the user's needs".
  • With the evolution of LLMs, the need for them is decreasing rapidly.

relevance

• next: Abstraction, speed and landing

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.