Comment

Comment by sandermvanvliet

I think this should be true for many things, or at least have a fixed future date at which you re-evaluate $thing

For example with Architecture Decision Records, put a 6 or 12 month expiry on them and evaluate to see if they can be renewed, should be changed or replaced with something that covers new insights.

Unfortunately that seems a very unpopular thing to do so I’ve never seen it work and companies end up with “we have always done it like this” type practices

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton