4 ms·
I made Dnote because even though I learn many things every day while coding, I forget most of them. The reason is that (1) I don't write them down (2) I don't r
by stockkid 10y ago
I made Dnote because even though I learn many things every day while coding, I forget most of them. The reason is that (1) I don't write them down (2) I don't revisit what I write down.
So I made a CLI to keep track of my engineering microlessons with minimal friction, without leaving the command line. Next step is to build automated digest email so that I actually remember my lessons.
I wrote more about why and how I am building it here: https://sungwoncho.io/making-dnote https://sungwoncho.io/making-dnote
- antjanus 10y agoThanks for posting it! I've been wanting to actually write an identical tool but for a daily diary.
- beaconstudios 10y agovery cool tool, I'll integrate it into my workflow this week and see what happens.
- baconomatic 10y agoLooks like a cool project! I noticed a small typo: > Reinforce your knowledge effor[t]lessly
- stockkid 10y agoFixed. Thanks for letting me know.
- 19eightyfour 10y agoI like the idea is being able to subscribe to other developers. If you could like or down vote notes, and if you could publish notes to channels ( i checked and you already have that, dnote use, to make a book ), and subscribe to devs channels it would be cool. I also think like a vim plugin that could bring up dnotes on Promise when you ctrl-something on the word Promise in your code, and a way to full text search, and if you automatically surfaced notes at intervals for learning, could be good ideas for this.