I would like to know your recommendation for a tool to track what you've learned this day/week/month etc.<p>Some sort of a service where you could easily write notes about the stuff you came accross while developing something.<p>For instance if I find a very useful link that shows me the correct way to do something, I would like to write that down somewhere with a simple explanation using my own words.
A few weeks ago there was a post[0][1] on hn from a guy who wrote a daily til for a whole year.<p>I stole his idea[1] and created jekyll blog on Github, I can just create a new .md file and put the things for the til down. With the new upload feature from github you can also just write the md file locally and just drop it in.<p>I like it so far, just need to get in the habit of writing it down daily.<p>[0] <a href="https://news.ycombinator.com/item?id=11068902" rel="nofollow">https://news.ycombinator.com/item?id=11068902</a>
[1] <a href="https://github.com/jbranchaud/til" rel="nofollow">https://github.com/jbranchaud/til</a>
[2] <a href="http://arminmsg.github.io/blog/til/" rel="nofollow">http://arminmsg.github.io/blog/til/</a> <a href="http://arminmsg.github.io/blog/til/" rel="nofollow">http://arminmsg.github.io/blog/til/</a>
Apart from keeping track, a related problem I'm facing is making sure that I am able to re-implement what I'm doing.<p>So what I do is the following:<p>1. I break down what I've learned into steps or checklists<p>2. I then put these into Scrivener<p>3. Each topic that I've learned has it's own page<p>Here's a small example from my notes around PDF generation + attachments in Rails. This is just the overall picture -- each bullet point expands to another bunch of notes which has actual code details.<p>* build a mailer with mail(to:, from: content:)<p>* build a controller what delivers that content<p>* the controller should render a notice that says that the post has been successfully created <via a respond_to method><p>* make sure that you configure the SMTP settings<p>* build a pdf creator (PrawnPDF::Base)
=> this initializes a PDF w/ some view_context<p>* configure a MIME type within config/initializers<p>* configure a controller that triggers a respond_to for this<p>* add a button that links to think Printable receipt<p>* save the PDF into some foldere<p>* insert a paperclip file type into the migration<p>* add this intot he user model<p>* go back to the PDF / order controller and then add a custom path to save the PDF (pdf.render file…)<p>* then save that file inside teh database & set it to the certificate
I usually just keep notes in plain text files and save the likes in an organized bookmark directory of folders so I can easily find relevant links. I do like what the other commenter suggested about the markdown files on github though, but I'm not sure what the best way to navigate those would be.
personally I use a local wiki to keep notes, links, research etc.<p><a href="https://github.com/gollum/gollum" rel="nofollow">https://github.com/gollum/gollum</a>