If You Didn't Write It Down, It Didn't Happen -- Take Notes
designbygravity.wordpress.com
designbygravity.wordpress.com
When we get to 10:00 (Our scrum runs from 9:30 - 10:00 AM) he announces "It's 10:00, and this meeting is done." and hits the Send Button on the email.
I realize that this can be all done on a Wiki, or other mechanisms, but it's surprising how _reassuring_ it is to know that I have on my laptop/iPhone a detailed list of all the strategic/Commitments/P1s/Sprints/Tasks that the org is worried about today/this week. Also, it's a very efficient mechanisms for the person taking notes. Their job is complete before we leave the room at 10:01 AM.
And, additional bonus - when I have my Staff meeting on Mondays, at 11:00 AM, half of that meeting is simply going over the relevant parts of the email that was sent out at 10:00 AM.
Like hamsters in a treadmill, just looking for the next two weeks, and never ahead enough. ( I know this by experience).
The scrum process is fine when dealing with bugs, or small incremental features, but it is very ineffective when dealing with completely new products or when trying to deal with innovative features.
Scrum throws all creativity out of the window. By creativity/innovation, I mean doing completely new things that are even a magnitude better, or just faster processes that what you have.
Creativity is a thing that just gets killed by planning. Often it happens when you are dealing with a problem. But the scrum process, puts blinders on developers, as you are supposed to work only on what you planned/committed to, and nothing else, like a good horse just watch the path you are told to by your manager/pm/team lead, and don't get distracted by anything else. Kills any instrict motivation, and sends a group towards a path of mediocrity as it delegates all decision making/creativity on the team lead (manager, or mp).
We use variants of agile at work. Daily stand-ups, email notes, two-week iterations. My daily standups look a lot like the grandparent, except they're at 4:00 PM instead of 9:30 AM and last only about 10 minutes.
But everyone recognizes that the process is there to guide us and not to constrain us. If your report is "I did nothing for the project today", well, that's your report. I had one feature where my report for every single one of the first 4 days was "I tried this and it didn't work." Followed by 2 weeks of furious coding where I didn't check anything in, followed by dumping 2500 lines on my code reviewer. I didn't get any grief from my coworkers (got lots of encouragement, actually), because they recognized that it was a hard problem, there were a lot of constraints, and we didn't even know what the constraints were until could put something up on the screen and start testing it.
It nails down my problem with most of the methodologies: they all do depend on people involved, yet there is very little talk about the right attitudes.
(FYI, according to Harvard Business Review and similar publications, the direct management is one of the main reasons why people decide to leave)
(BTW, why you downvoted him?)
If there's a meeting, or whatever, it means that my output will be seriously hurt. That's another problem with such methodologies' descriptions: it is very tempting to response me that I don't fit to the team or I should try to change my habits, even if, in the right environment, I'm always the most productive team member.
Also, I work in an operational organization, so, a lot of our design patterns are pretty well laid out, and so most of the creativity comes from improving the patterns (which we do in design review or our bi-annual architecture refresh) more than creating anything particularly innovative during the week. We're mostly focused on execution and hitting commitments - and tracking them and writing them down at the beginning of each morning makes sure we know, and hit those commitments.
I keep it mundane: I did this, then I did that, and after dinner, I did this. If commentary occurs to me, I'll jot it down, but if not, a Joe Friday "just the facts" transcription will do just fine. It usually takes only a few minutes. And yet reading entries even a year old can be fascinating: the amount you will forget in a year's time (to say nothing of a decade) is enormous. Even recording just big-picture outlines of day to day life makes a great journal.
Do you use a paper journal or an electronic one? I used to use composition books, but last year I switched to digital since I can easily back it up. My system is just text files in a directory hierarchy:
ggreer@carbon:/Volumes/DIARY/2010/01$ ls 02.txt 03.txt 04.txt 05.txt 06.txt 10.txt 11.txt ...
In the rare event that I want to draw something, I'll draw it on paper and scan it or draw on a whiteboard and take a photo. I prefer text though, since I can grep -r it.
Right now, I use paper. I do create backups (photocopies), although whether I'll buy another paper journal when I fill this one is an open question. One advantage that paper has is that, if properly preserved, it's quite durable; it's not vulnerable to file system changes or anything. A disadvantage is that it's laughably easy to destroy in a flood or fire, whereas data can be searched and backed up.
I also have some irrational quasi-romantic attachment to a journal written in my own handwriting, but I'm probably going to need to let that go.
It gets synced to Dropbox, and is also a hg repository that I intermittently push to a server for safekeeping. Honestly I've very rarely wanted to check the revision history, but it's there if I need it. [and another advantage of plain text].
It may sound over-elaborate, but that's just because it's grown over the years according to what i've needed. I'll probably add some kind of lightweight tagging/search system soon, if only because at >1m words, it's reaching the point where grep is a bit sluggy. And it's hard to overstate the benefits of having a view of my daily life, year by year.
Completely mouse-free and uncluttered. Also, it doesn't make the mistake to organize the notes, since this is usually impossible and a waste.
EDIT: web-page seems down, check Github instead: http://wiki.github.com/scrod/nv/.
http://www.yworks.com/products/yed/
and Quotepad for simple text note-taking
Fact is, paper is probably the most versatile way to take notes, because when you need a graph or an equation, you don't have to muck about entering data points or writing TeX equations, you just draw/write the thing. You don't have to worry about formatting or anything like that.
Is there any good note-taking software where I can write equations, either as latex or something similar?
Thanks =)
- if there isn't a network connection, that isn't a fail. You can use native client in offline mode, and the data will be synced next time you will be online.
- the notes does automatically open in editing mode. (at least in version 3.1 I use).
It's done wonders for my productivity having to make constant critical notes. Especally if you have to go back to a problem after a break.
It's also a brilliant metaprogramming language (i use it for html, java, javascript, python, sql, mozart/oz) so you can spend all your work time in it if you're a programmer.
I'm not sure it's cut out for everyone though
hackernewscomment_paragraph_id("I use prolog written in text files, it's pretty much the perfect query language and so there's no better tool for organizing your knowledge. (it's such a cool way to organize notes that i often go overboard with taking too many notes and too much organizing).",1,1030).
hackernewscomment_paragraph_id("It's also a brilliant metaprogramming language (i use it for html, java, javascript, python, sql, mozart/oz) so you can spend all your work time in it if you're a programmer.",2,1030).
comment_tag(1030,prolog). pllanguagecomment(X) :- comment_tag(X,Y),pllanguage(Y). pllanguage(prolog). pllanguage(java). description(pllanguagecomment,"tell me comment id's where i commented about a programming language").
This is very relevant to my interests. Please post or write an article about this.
I started using Org mode in Emacs recently.
Anyone have any experience for the best way to use Org mode for note taking?