Se il codice non è più tuo — When code is no longer yours

Salvatore Sanfilippo explores a possible social benefit of coding agents: when developers no longer write every line themselves, they may find it easier to replace an implementation without treating the change as a rejection of their own work. His distinction is between caring about a project's purpose and design and becoming attached to the particular code that implements them.

This English summary is editorially translated from Italian auto-generated captions, without an independent audio or visual review. Sanfilippo develops an idea he attributes to a DHH tweet; the tweet itself was not independently checked. He mostly works alone and presents the team benefits as a hypothesis, not measured results.

Key points

• Implementation effort can turn a technical disagreement into a personal loss. Sanfilippo describes a developer who has spent months producing working code and resists a better approach requiring a radical change because adopting it would mean discarding that effort. The mechanism he proposes is emotional attachment: the difficulty, satisfaction, and accomplishments associated with writing the code make it feel intrinsically valuable, even when another implementation would serve the project better. This is his account of one source of resistance, not a claim that every rewrite is justified. 00:56–04:41(opens in a new tab)

• Generated code may make collective ownership easier to practice. He reads DHH's observation as a suggestion that LLMs can help deliver the shared ownership of code that teams have previously sought. Once a team agrees on design ideas, its generated implementations could be treated as replaceable shared work rather than territory belonging to whoever produced each part. He expects this reduced attachment to make radical changes and previously untried approaches easier to consider; he does not report a team experiment demonstrating that effect. 01:48–02:54(opens in a new tab), 06:29–09:36(opens in a new tab)

• Letting go of an implementation does not require letting go of the project. Sanfilippo says he was already more attached to software ideas, efficiency, and simplicity than to exact code, which is why the observation initially escaped him. He still feels strong ownership of his projects. His example is accepting someone else's better implementation of the same feature, provided it does not distort the project's character: replacing generated lines can preserve the design he cares about. 04:41–06:29(opens in a new tab)

• The predicted benefit is less interpersonal friction, not a demonstrated improvement in software quality. He speculates that developers could spend less energy defending their own implementations and more on contributing new design ideas. He explicitly acknowledges limited team experience, asks whether viewers have seen attachment obstruct change, and remains curious about how these relationships will evolve. 07:32–09:36(opens in a new tab), 10:35–11:02(opens in a new tab)

Full video: https://www.youtube.com/watch?v=v0WVsLQo3-k(opens in a new tab)