It may sound like stating the obvious, but it’s important to separate the perceived value of oneself as a developer looking at things from a bird’s-eye view and the value felt as a user.
-
This awareness might be necessary for oneself at the moment.
-
“The value perceived by oneself as a developer looking at things from a bird’s-eye view”
- To put it bluntly, “whether it would be interesting when explaining this as a paper.”
-
“The value felt by oneself as a user”
- Whether you would want to use it even if you had to pay for it, for example.
-
Confusing these two is common, where one may be driven by the former’s motivation but the latter doesn’t exist.
-
In the context of service development, there is often talk about “first creating what you want for yourself.”
- Such as Egocentric design.
- It’s good if it’s something “you would want to use even if you had to pay for it,” but if it’s something “you find interesting from a bird’s-eye view,” achieving the goal becomes difficult.
-
LLM Podcast and Fractal Summarization are intended to be more of the latter.
- While sometimes the former may get mixed in during the creation process, it seems crucial to clearly distinguish them in your mind.
-
Medium Chat, for example, is currently entirely the former.
-
The former becomes “the reason for creating something” but not necessarily “the reason for using it.”
- (It might become “the reason for someone other than yourself to use it” haha)
- For example, paying participants in an experiment to use the system you created.
- This approach works well for science and art.
- (It might become “the reason for someone other than yourself to use it” haha)
-
The latter serves as both “the reason for creating something” and “the reason for using it.”
-
It’s fine to explore with the former, but the intersection with the latter is crucial.