I see two parts in your question, and I'll answer both with the same tool.
I use Emacs and Org-mode to track my tasks and do my documentation:
with my task file, I have a list of TODOs for the coming days, I can set schedule dates as well. Once those tasks are done, I archive them (one shortcut) and move one. I check that file multiple times a day.
with documentation, I have multiple files per project (each in a separate folder). It could be notes of modifications (change log), research of data (memo of reference material I found + quotes), debugging (problem notes and investigation procedure)
The beauty of that method is because org files are plain text, all can be grepped and it's easy to find a fix I did a few days back, then redo the same for another project.
Also, org-mode allows to include sample code that can be executed right from Emacs and have the results in the buffer as text result (works with data bases as well!). I simply exports all that in HTML and share with my team.
There is a learning curve to that method if you're not familiar with Emacs already, but it's very worth learning it IMO.
cedric simon
Web dev
I see two parts in your question, and I'll answer both with the same tool.
I use Emacs and Org-mode to track my tasks and do my documentation:
The beauty of that method is because org files are plain text, all can be grepped and it's easy to find a fix I did a few days back, then redo the same for another project.
Also, org-mode allows to include sample code that can be executed right from Emacs and have the results in the buffer as text result (works with data bases as well!). I simply exports all that in HTML and share with my team.
There is a learning curve to that method if you're not familiar with Emacs already, but it's very worth learning it IMO.