33 ms·
Worst: you find your own answer that says: “Nvm, fixed the issue.”
by 404mm 4y ago
Worst: you find your own answer that says: “Nvm, fixed the issue.”
- vivzkestrel 4y agothis is why I have made it a point these days that when I fix an issue, I immediately go to all the forums, subreddits and stackoverflow sites where I posted the question and post the relevant solution. Its a lot of work but totally beats figuring out what you did 6 months later
- hipjiveguy 4y agoI make a habit of turning every question I have, that I don't find an answer to in 30 min, a question AND answer on stackoverflow/stackexchange And many times, even years later, when I google the answer, I google my name, stackoverflow, and the topic, and kapow - answer received :D
- hinkley 4y agoThat’s just karma. I have tried not to do that to myself because so many others have done it to me. Still, sometimes the answer I left is too vague to be practical.
- AceJohnny2 4y agoI have a notesfile on how to fix/debug things. When I started it, I would write things down after I fixed something and figured I'd need to remember it later. Problem was, I would often forget to write things down, or naively think "that was quick to find out, don't need to write it down", which is a classic mistake of confusing post-facto mindset with pre-facto. So now when I wonder how to do a thing, I first write down in my notesfile what my question is, so when I do resolve it I go and write down the answer to satisfy my need for closure.
- SamPatt 4y agoThis is the way. I make a new markdown file for every program / VPS login command (the entire SSH command with custom ports), and really anything which I know I would need to search through bash history down the road to do it again. Those files are sorted into a handful of folders which allow me to quickly find all these programs / commands quickly.