2
0 Comments

How do you keep track of programming resources you've used in the past?

I find that each time I start a new project I end up needing to visit a lot of the same resources again, and haven't landed on a good process for keeping track of them all.

Do you just bookmark a bunch of pages (articles, tutorials, stack overflow posts) like I do?

Do you take notes somewhere to provide context on how you used the code and any changes you had to make to get it to work, etc?

Or do you find yourself trying to get back to the same stack overflow answer you found 3 months ago? I've had this happen to me several times.

  1. 1

    This comment was deleted 6 years ago