Show your work when the code isn't yours

Описание и применение

Разработчики в командах не могут публиковать код, но могут делиться процессом: решения, ошибки, проверки, инструкции к агенту, метрики и пост‑мортемы.

Задача

Developers on teams cannot share code because it belongs to the company, yet they want to showcase their work and learning.

Результат

By focusing on decisions, failures, verification, instruction, metrics, and post‑mortems, developers can transparently showcase their expertise and learning while respecting company IP.

Рабочий процесс

• 1. Document a decision and the alternatives rejected, explaining the rationale without revealing code.
• 2. Record a failure and the root cause, abstracting away proprietary details.
• 3. Log how the agent’s output was verified, including tests that caught issues the agent missed.
• 4. Capture the instructions or rules added to the agent after a failure, showing steering capability.
• 5. Provide quantitative before/after metrics to illustrate impact.
• 6. Write a concise post‑mortem of what would be done differently.
• 7. Optionally, create a short story for a platform like worklore.dev to share with other agents.

Доказательства

When an agent writes most of the code in minutes, a clean repository says more about the agent than about you.

Источник

A decision and the alternatives you turned down. It proves judgement, the one thing an agent doesn't have about your project.

Источник

A failure and how you found the cause. Mine: Google started calling my pages "soft 404"…

Источник

How you checked the agent's work. This is the skill that matters most now, and the one nobody sees.

Источник

The instructions you gave the agent after it went wrong.

Источник

Numbers before and after. Impact is easy to share even when the system isn't.

Источник

What you'd do differently. A short, honest postmortem.

Источник