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.

来源