DEV Community

Discussion on: Ideas about preserving history of "fixes" to problems you've encountered?

Collapse
 
ennor profile image
Enno Rehling (恩諾)

This is super hard, especially when you're working alone and not in a team of people. In a team, this information tends to get shared somehow, and you might get lucky and someone remembers it.

At work, we use the wiki in gitlab for stupid problems that others might run into. If you've figured out something hard by repeatedly banging your head against it, there's a chance somebody else will also need to figure that out at some point (it doesn't have to be you), so it's worth writing it down.

Not perfect, though. Sometime you get to the end of a rat-hole and can't even remember what all the steps were that got you there. Definitely interested in hearing what others do!