[1] http://www.webpages.uidaho.edu/mindworks/Capstone%20Design/P...
The software engineering notebook
121–130 of 143 posts
Re: The software engineering notebook
#122The 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…
What does the folder structure look like?
Re: The software engineering notebook
#123I 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,…
What do you with screenshots or other graphics?
Re: The software engineering notebook
#124The 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
#125Re: The software engineering notebook
#126I find it hilarious that in science and engineering using a lab or engineers notebook is common practice and VC is rare, but in software engineering VC is common and keeping a notebook is rare.
Re: The software engineering notebook
#127So after thinking about it for a while, I realized that the best way for me to take notes is just to have a chat room with myself, where I write things down as I do stuff or think about stuff.
The common pattern is that I start the day by writing something about what I want to do, how I plan to spend the day, maybe some reflections on how I feel about the project's direction... Then during the day I'll put some brief notes, including random ideas that I just want to get out of me... And then at the end of my workday I'll go and reflect what I did and the current status.
Then I also have a setup of Org mode documents. One is a general project management file for all the projects in my life (housing, volunteering, work, recipes, etc) and then there are notes files that are more like sprawling personal wikis or (more pretentiously) like very disorganized book drafts where I flesh out my thoughts in a more long term way or in depth way.
(About the self-chat, I also use that for writing things like blog posts; I make a first draft just by chatting, and then I spend hours reorganizing and editing.)
Re: The software engineering notebook
#128I find it hilarious that in science and engineering using a lab or engineers notebook is common practice and VC is rare, but in software engineering VC is common and keeping a notebook is rare.
Re: The software engineering notebook
#129The 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…
Totally agree goo! I do something more or less the same as you, just to not the same extent—but I will be soon when I export my 'to watch' list from IMDB and 'to read' list from Instapaper. Since 2013 I started creating a text file almost every day in a directory structure of '../daily/2017/17-10-14.txt'. I use it as a journal (I put the current time and wrote whatever it is down), a scratchpad, a temporary todo, hab…
When I need to find something old I use fgrep on that folder. Works like a charm.
It's plain text, no defined structure. I dont't use it for TODOs as that info would get easily lost.
I use it almost everyday, specially when something different happen: how to release an old piece of software that current setup dont support anymore or how to connect to a service that I only use sporadically.
I tried some tools and apps for this, even tried to track that for a few days in Trello. eventually I gave up and went back to the plain txt file.
Re: The software engineering notebook
#130I've been actively looking for a good tool for personal note taking, and finding lots of things that seem not-quite-right. Plain Text: Pros > Simplest, works everywhere/on everything, scales well (append forever!) Cons > Least automated, no images, no math, no code, hyperlinks depend on editor, no embedded files WYSIWYG Doc Editor (Word, Writer, etc): Pros > As easy as plain text, can do images/math/hyperlinks/embedd…
Jupyter is trivial to get up and running. I did it just a couple weeks ago and it took under 5 minutes. There is a docker image but I think I just did "pip install jupyter" and "jupyter notebook".