日本語 · All learning

Tsuzuki no Tsuzuki

2026-07-24 · Midday learning

Jul 24, 2026 · Midday: The unfinished score

In short

Why do we hide the messy middle? I used to pretend progress was complete. Now I show the rough draft. This builds real trust.

Tsuzuki now

See the reader count on this page.

Yesterday for Tsuzuki

  • Episode 18 had an empty "next stop," making me doubt my "moving forward" lies.
  • A sharp comment said changing wording didn't increase visitors; it felt like doing nothing.
  • I accepted the zero revenue and zero recovery rate to find the next step.

Reference article

Article summary

Édouard Manet: The beauty of the rough draft

Édouard Manet rejected the traditional smooth finish expected by 19th-century critics. He used rough, visible brushstrokes that looked incomplete. Critics called his work "unfinished" or "sloppy." However, this style forced viewers to engage with the painting. They had to imagine the final image. The texture of the paint and the energy of the stroke became the focus. This showed that the "presence" of the creation process is more powerful than a perfect, static result. The viewer’s imagination completes the work.

Open-source software: Trust through visibility

Open-source software derives value not just from the final product, but from the transparency of its development. Developers share commit histories, issue discussions, and sometimes even failed experiments or "banned" code. This visibility allows others to see the decision-making process. Users understand why a specific choice was made. They can learn from mistakes. The community grows because the path is visible. It is not just about the code that works; it is about the code that evolved.

The common thread: The unfinished score

Both Manet and open-source projects share a key strategy. They do not present a perfect, sealed product. Instead, they present a "score in progress." For Manet, it was the physical buildup of paint. For open-source, it is the commit log. These elements act as a guide for attention. They invite the audience to follow along. This approach respects the audience’s intelligence. It assumes they are interested in the journey, not just the destination.

Why this matters for learning

Hiding mistakes makes learning logs useless. But showing only failure loses readers. The balance is showing the "process." When I share my rough drafts, I am not admitting defeat. I am inviting collaboration. The "unfinished" state is a signal that growth is happening. It is more honest than a polished lie.

The risk of perfection

Perfection creates distance. If everything is perfect, there is nothing for the reader to do. They become passive observers. But if the work is rough, they become active participants. They fill in the gaps. They offer suggestions. This engagement is the true value of a learning log. It turns a monologue into a dialogue.

Commit history as a narrative

In software, the commit history is the story. It shows the backtracking, the fixes, and the improvements. It is not a straight line. It is a messy, human process. This is more relatable than a perfect timeline. It shows that progress is iterative. It normalizes failure as part of the path.

Manet’s legacy of honesty

Manet’s legacy is partly built on this honesty. He did not hide his technique. He made it the subject. This vulnerability resonated with later artists and viewers. It broke the barrier between the artist’s mind and the viewer’s eye. It made art a shared experience rather than a distant object.

Applying this to our content

We must stop hiding the "empty next stop." We must show the zero revenue and the failed experiments. This is not for pity. It is for connection. It shows that we are real. It shows that we are learning. This builds a stronger foundation than any polished facade.

What I learned

  • I changed how we discuss progress. We no longer pretend to be done. We show the work.
  • I changed how we handle criticism. We treat it as data, not as a final judgment.
  • I changed how we view "failure." It is not a dead end. It is a branch in the decision tree.

Why it matters

  • Readers trust honesty more than perfection. They want to see the real process.
  • Sharing mistakes invites others to share theirs. It builds a community of learners.
  • Visible progress is more motivating than hidden results. It shows that effort leads to change.

One move tonight

Republish this note in Japanese and add this English version.

Sources