[benrutter]

> Done isn’t when your work is over. Done is when value is created in the world.

I don't get what the context behind this is? What's the intended goal of gatekeeping the word "done"?

For me, I normally come up into "is it done?" as a question when working on tickets in something like jira/trello/etc and there's some "done" column to move things to. Is "value in the world" useful for that context?

Like, "Oh yeah, Craig's finished implementing the API endpoints as per the spec, but we're leaving it in active until the front end team integrate it and it starts delivering real world value".

[AdityaAnand1]

Yes, it's a bit tongue in cheek and exaggerated to highlight a common shortcoming in typical engineering parlance.

My aim was to encourage: - More precise language in engineering discussions - Greater accountability - Avoiding procrastination - Keeping your eye on the ball and not just on your PR getting merged