I have a "notes" directory in dropbox. I use .md files, with a text editor that does some highlighting based upon the markdown. 95% of them go into what I call my "dev diary". Each day gets a new file. Any questions, answers, thoughts, etc. while programming or designing go in there. For searchability, I also add any reference Jira/Trello/etc ids. Beyond that, I have cheatsheets and checklists. Cheatsheets are short,…
The software engineering notebook
81–90 of 143 posts
Re: The software engineering notebook
#82Earlier quoted context omitted.
On the other hand, based on my personal experience, maintaining a constantly growing archive of things, be it notes, bookmarks, emails, etc. turns out to be not very useful. Also, it gradually becomes something that you spend more time on than on other things. I now prefer to be more spontaneous, try to minimize the number of things that drag me into the past, start things as if from scratch, "reset" myself, dismiss…
I had the same problem as you, but my solution was separating "notes" from future actions. My notes track knowledge, they are referenced as-needed so I store everything because there's low/no cost. I've also found that writing things down improves my recollection, so there's value even if I never reference the note again. My calendar / omnifocus track future actions, I minimize these and keep them very well curated -…
I'm curious about what this means. What are "do" notes (as distinct from "todo" ones). If it means that don't calendar, and you just do that task immediately, how you plan and (more importantly) remember future tasks?
Re: The software engineering notebook
#83Re: The software engineering notebook
#84The commitment to taking good notes has been one of the best decisions of my life -- not just professionally. I use my standard text editor (Textmate 2), and have a "notes" project, with all manner of categories organized by folder. I take notes on articles I have read, take notes on any presentations I watch or educational courses I take, or books I read. Moreover, I now take much better in person notes -- I take th…
Re: The software engineering notebook
#85Earlier quoted context omitted.
A script might finesse things a little more, but you could get a naive implementation of the timestamp behavior with something like: alias journal='vim + "/Users/username/journal/$(date +%Y)/$(date +%Y%m%d).md" -c "execute \"normal! Go$(date +%T)\ ========\ \" | startinsert "'
This command (as presented) is giving me issues with saving the file on my machine, not sure if it's specific to only me but figured I'd give you a heads-up!
alias journal='mkdir -p /Users/insert_your_username_here_on_mac_on_linux_change_Users_to_home_on_windows_good_luck/journal/$(date +%Y)/; vim + "/Users/insert_your_username_here_on_mac_on_linux_change_Users_to_home_on_windows_good_luck/journal/$(date +%Y)/$(date +%Y-%m-%d).md" -c "execute \"normal! Go$(date +%r)\========\\" | startinsert "'
Re: The software engineering notebook
#86Earlier quoted context omitted.
On the other hand, based on my personal experience, maintaining a constantly growing archive of things, be it notes, bookmarks, emails, etc. turns out to be not very useful. Also, it gradually becomes something that you spend more time on than on other things. I now prefer to be more spontaneous, try to minimize the number of things that drag me into the past, start things as if from scratch, "reset" myself, dismiss…
I had the same problem as you, but my solution was separating "notes" from future actions. My notes track knowledge, they are referenced as-needed so I store everything because there's low/no cost. I've also found that writing things down improves my recollection, so there's value even if I never reference the note again. My calendar / omnifocus track future actions, I minimize these and keep them very well curated -…
Re: The software engineering notebook
#87Re: The software engineering notebook
#88* Leave the office once you're really sure that deployment was successful
* Have timestamps in logs
* Before making your opinion public, make sure what you think is a mistake is in fact a mistake
* When you struggle with an issue, make sure the fix isn't right in front of you
* Make sure everything's set up for remote work; you don't want to hotfix some production issue at 2 AM, only to find out you can't access Git from home
* Other people's time is worth twice yours
Re: The software engineering notebook
#89The commitment to taking good notes has been one of the best decisions of my life -- not just professionally. I use my standard text editor (Textmate 2), and have a "notes" project, with all manner of categories organized by folder. I take notes on articles I have read, take notes on any presentations I watch or educational courses I take, or books I read. Moreover, I now take much better in person notes -- I take th…
Re: The software engineering notebook
#90Back in college, going for my BSEE degree, the professor or lab assistant were constantly stressing the need to record everything done at the bench in a log book with pages dated and signed. Part of this was to keep a history of lab experiments and remind you of what you did and/or learned. Really, however, it was to develop the habit to carry over into your professional career. There are many examples of this but th…
What's the signature for?