The great thing that a site like this can bring is helping to discover and refine anti-patterns [1]. I am a huge fan of showing valid paths to take to speed up learning, but showing dead ends, or at least sub-optimal paths, is often very helpful as well.
One criticism I have though is that documenting a failure doesn't mean you actually realized what truly went wrong and even if you accurately describe what went wrong that doesn't mean you have a real solution to that problem. Often the reason things went wrong were far more nuanced and the fix is not obvious. Adding an untested lesson at the end of each of their failures is premature. I'd call them, at best, observations and next steps to try. They are only lessons after they have truly been tested and successfully navigated around the original failure.
jmward01•36m ago
One criticism I have though is that documenting a failure doesn't mean you actually realized what truly went wrong and even if you accurately describe what went wrong that doesn't mean you have a real solution to that problem. Often the reason things went wrong were far more nuanced and the fix is not obvious. Adding an untested lesson at the end of each of their failures is premature. I'd call them, at best, observations and next steps to try. They are only lessons after they have truly been tested and successfully navigated around the original failure.
[1] https://en.wikipedia.org/wiki/Anti-pattern