Hacker News new | ask | show | jobs
by abraininavat 4574 days ago
The problem with putting everything in Evernote is that it becomes stale. I think that's what has prevented me from getting into it.

Some examples of items I would not put in Evernote, from the article:

- Some sections of my server's log, containing all the information I need to troubleshoot my most recent problem

You copied some sections of your server's log and put them in Evernote, so that you can troubleshoot a problem? How is this useful? Why not troubleshoot it by looking at the logs directly? Why do you want to store stale logs? Or, are you saying your server automatically refreshes the Evernote note? That would be more interesting and worthy of an article.

- A web clipping from an article on the best VPN providers, since I'm installing a VPN on my home server

Aren't you interested in whether the list of best VPN providers changed since the last time you searched? And why store something that's a google search away? How often will you need to review this stale list of VPN providers?

- A web clipping on how to install OpenVPN on my home server, since I don't remember how to do it by heart

Same thing. https://www.google.com/search?q=how+to+install+openvpn How often do you install OpenVPN?

- A web clipping on setting file permissions, since I need to give my girlfriend access to my server's files

What about just learning how to set file permissions, if it's something you do very often? Or, "man chmod".

No offense intended, I know people think and work differently. I just still don't get it.

1 comments

+1 here. We use Evernote for documentation but we also spend hours and hours each month maintaining it. That said, "How to install XYZ?" is valid documentation - it might be that a specific way works on your setup and that it took 25 articles/posts and three days to figure that out. The key thing is to maintain the documentation - cull the old, update what you keep.