Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The software engineering notebook

winterflower.github.io

Post reply on HN
Print view View original

91–100 of 143 posts

Re: The software engineering notebook

#91

Post by krallja »

Koshkin wrote: post #27
colechristensen wrote: post #10

Earlier quoted context omitted.

This is true and somewhat infuriating. I have a $700 computer in my pocket and the best way to write a grocery list is on a post-it found in the kitchen drawer. I think it comes down to the human interface of a touch screen being slow, frustrating, and generally inefficient.

... and your 700-dollar pocket computer is probably not much better than the 200-dollar one that you ditched a couple of years ago. We buy things not because we need them, but because we want them. (Why we want them is another story.)

I mainly upgrade my phone for the camera upgrades, if I'm being honest with myself.

Re: The software engineering notebook

#92

Post by krallja »

Koshkin wrote: post #63
nvarsj wrote: post #40

Earlier quoted context omitted.

Get a Samsung Note 8. Use wacom pen to take notes. Carrying around dead trees is archaic.

Reminds me of the anecdote about the Russians using a pencil in space (vs. a $1000 pen specifically designed to work in weightlessness).

Snopes: FALSE

http://www.snopes.com/business/genius/spacepen.asp

Re: The software engineering notebook

#95

Post by bootcat »

I think jotting down very important points we realized while developing is worth noting down. May be in a gitbook. But having an actual paper or notepad journal and noting down everyday things is too much data and we rarely, and i mean like very rarely look at that a second time !

Re: The software engineering notebook

#96

Post by hyperpallium »

goo wrote: post #13

The 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…

How do you find relevant notes from the past? grep (or a fuzzy-match version) would help, or do you organize them by some system?

The organization of notes in an accessible manner is a challenge for me - perhaps I'm doing it wromg.

Re: The software engineering notebook

#97

Post by mursil_syed »

I use dokuwiki for keeping my important notes. Dokuwiki is free and file based. I use git for disaster recovery.

I used to host dokuwiki on my own machine but recently I have moved dokuwiki running inside a docker container on one of my AWS instance.

Re: The software engineering notebook

#98

Post by bluetwo »

qrbLPHiKpiux wrote: post #3
forkLding wrote: post #2

Is there any opensource things that can be a software engineering notebook or journal that is easy to use and painless?

A plain paper notebook. I’ve tried everything and nothing works as well.

I also use paper. So there are two of us. 8x11 notebook of quarter-inch graph paper.

Useful for taking notes wither portrait (in meetings) or landscape (in front of a computer). Also graph paper obviously helps with sketches and dividing up the page on the fly.

Re: The software engineering notebook

#99

Post by d08ble »

I'm using LiveComment structured notes for everything. I developed a methodology how to use it across multiple operation systems & technologies. LiveComment extend my memory & speedup developing source code. It has powerful server/client plugins system for add any function in runtime with live reload. I'm using paper & board for brainstorm too.

https://www.npmjs.com/package/livecomment

Samples here:

http://acpul.org/livecomment-src - livecomment js sources (it's quine, that developed using self documented code)

http://acpul.org/pool - common memory pool: active info, some processed bookmarks from HN, reddit, etc.

http://acpul.org/pica - livecomment in real project. here is collected info when i was develop gpu optimizations for popular nodejs image resizing library https://www.npmjs.com/package/pica

Re: The software engineering notebook

#100

Post by MichaelBurge »

lucideer wrote: post #82
losteric wrote: post #58

Earlier quoted context omitted.

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 -…

> no "todo", only "do" 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?

In practice, most people's "todo" list ends up being the garbage bin for low-priority items that they'll never actually do. It's worth separating the things you actually plan to do next week/month, from the ones in a "backlog".

Grep any large code repository for "TODO" comments.

Post reply on HN