NEW: For a prettier blog interface, see the Wordpress version!
- Thinko: Incentives for open-source adoption 08:14
- Reflections on study methods 16:53
- Kanji 28: Practice writing, first pass
- Kanji 28: Practice writing, second pass
- Kanji 26, 27: Review
- Japanese food event in the Philippines 18:00
- Kanji reflection 18:12
- Notable people who use Emacs 19:47
- Study reflections 21:12
- Time division 21:25
- Linux certification 22:48
| 9:00 | 12:00 | Class |
| 13:30 | 16:30 | Class |
| A1 | X | Combined pass |
| A2 | X | Kanji 29: First pass |
| A3 | X | Kanji 29: Copy compounds onto paper |
| A4 | X | Chuukyuu 17 |
| A5 | X | Chuukyuu 16 |
| A6 | X | Kanji 28: Combined pass |
| A7 | X | Kanji 26, 27: Review ... |
| A8 | X | Kanji 28: Copy compounds onto paper |
| A9 | X | Kanji 28: Practice writing, first pass ... |
| A10 | X | Kanji 28: Practice writing, second pass ... |
| B1 | X | Go to Jusco to buy 4 sets of 2 word rings, maybe eat dinner before clocking out of this task |
| B2 | X | Hack quick prototype for multiple tasks (TaskPool) |
| B | X | Fix embarrassing bug: E-Mail from Chris Parsons |
| A11 | C | Work on FurtherStudies from 2004.11.28 |
| C1 | C | Check out EmacsWiki#RecentChanges from 2004.11.28 |
1. Thinko: Incentives for open-source adoption: 08:14
Because site licenses depend on the number of seats, I'd keep a running count of the people who signed up for the program so that we can see the prospective savings. I'd pass those savings directly to the employees' monthly salaries so that they can see the effect. It'll cost more initially--think of this as the cost of training.
This makes the benefits of open source tangible and rewards people who are open to change.
I'd keep at least one Windows machine with Microsoft Office around so that people have somewhere to go when a client sends them something braindead. However, I would post a sign warning people about viruses, and do an anti-virus sweep frequently (every night?). The results of this would be posted.
2. Reflections on study methods: 16:53
| 0:38:30 | Kanji lesson 25: Review |
| 0:39:38 | Take my laundry down and iron it |
| 0:02:43 | Kanji lesson 25: Second review |
| 0:38:12 | Kanji lesson 26: 1st pass |
| 0:22:07 | Dinner |
| 0:31:04 | Chuukyuu homework 13 |
| 0:06:35 | Kanji lesson 26: 2nd pass |
| 0:18:56 | Chuukyuu homework 14 |
| 0:31:12 | Kanji lesson 27: 1st pass |
| 1:08:55 | Chuukyuu homework 15 |
Perhaps I can use electronic flashcards instead, although I won't be able to sort it that easily. Instead of sorting, I can perhaps skip over stuff I already know. Using flashcard.el's Leitner method will result in overdrilling again. I should practice writing based on the reading, as that will also take care of making sure I learn onyomi.
Maybe I should make two passes per group of five kanji, then one pass through the whole thing. After that, I'll do the homework. Review is done as one pass of writing through the whole thing.
I'm almost out of word cards. I'll need to either stock up on them or think of an electronic way to do this. I need quick access to the correct answer and a way to keep track of my progress. I have to resist the temptation to hack up something quickly. I shouldn't be thinking about writing a program to do the job. (Once a programmer, always a programmer)...
Mmkay. As for optimizing my chuukyuu homework: I should probably fill the vocabulary part all in one go. If I keep the computer open, I can use it to look up pronunciation. I should also review all of the grammar using the web-based training notes, as they provide just the bare essentials. When in doubt, I can turn to the paper version.
Today:
- Get my Chuukyuu chapter time down to 20 minutes.
- Break down my kanji study time into the time it takes me to copy the
kanji down, the time it takes me to make a first pass and the retention rate of such, the time it takes me to make a second pass, and how much time until I feel reasonably happy with my progress.
- Use another method for my second set of kanji: groups of five in
between Chuukyuu questions. Track total time.
6. Japanese food event in the Philippines: 18:00
Invitation to Tabemono Fest
Juujiro J-Culture Organization, Inc.
cordially invites you toTabemono Fest: A Festivitiy of Japanese Cuisine
Saturday, 11 December 2004
at Crisanta Towers, Pasig Cityprogram starts at 12:00 pm
there will be cooking demos, on-the-spot cooking contest, extreme ramen eating contest, free food taste and recipes.
entrance fee is P70.
for pre-registration and inquiries, email us at juujiro_ml@yahoo.com
THANK YOU,
Juujiro Officers
E-Mail from Anuerin Diaz
7. Kanji reflection: 18:12
| 0:08:46 | Kanji 28: Copy compounds onto paper |
| 0:05:16 | Kanji 28: Practice writing, first pass ... |
| 0:02:05 | Kanji 28: Practice writing, second pass ... |
| 0:03:14 | Kanji 29: Combined pass |
| 0:09:18 | Kanji 26, 27: Review |
8. Notable people who use Emacs: 19:47
- Richard Stallman (founder of Free Software Foundation) is an Emacs user. Hint: He is the original author of Emacs, after all. :-)
- Yukihiro Matsumoto (creator of the Ruby programming language) is an Emacs user. Hint: He said so in a post to ruby-talk mailing list. Quote from http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/108051: "I wrote ruby-mode.el; I live in Emacs; I program in Emacs; I debug in Emacs; I read mails in Emacs; I wrote MUA for Emacs."
- Jeremy Zawodny (author of "High Performance MySQL") is an Emacs user. Hint: He wrote Emacs Beginners' Howto (http://jeremy.zawodny.com/emacs/).
- Andrew S. Tanenbaum used elle. It is some clone of emacs. Then
he moved to emacs. He said so in his homepage. http://www.cs.vu.nl/~ast/home/faq.html "Which editor do you use for producing books? I used to use elle, a stripped down emacs clone, but I finally decided to take the plunge and move up to full emacs."
- James Gosling, father of Java, currently CTO at Sun's Developer Products Group, uses Emacs. Hint: He wrote a C-based Emacs implementation in 1981 (the code portions of which became GNU Emacs). ... Uh, no. He was one of the reasons that the GPL and copyright assignments were invented. His code had to be removed from Emacs and substantial portions rewritten by Stallman, because he refused to let his stuff get distributed by the FSF.
- Jamie Zawinski, one of the main coders for Netscape Navigator and one the founders of the Mozilla Foundation, uses Emacs. Hint: He wrote Lucid Emacs. There's an Emacs timeline document on his website, http://www.jwz.org/ ... So you can bet your sweet *** that he is not using Emacs, but rather XEmacs (which is the successor of Lucid Emacs).
- Guy Steele. Co-inventor of Scheme, author of "Common Lisp the
Language", co-author of the Java language specification, first person to port TeX, served on the standards commitees for C, Fortran, Common Lisp and Scheme. And finally designer of the original Emacs command set.
- John research. (proof: http://www-formal.stanford.edu/jmc/facts.txt). - SF writer Neil Stephenson uses Emacs for some of his books
http://www.cryptonomicon.com/beginning.html "I use emacs, which
might be thought of as a thermonuclear word processor." - Donald Erwin Knuth (creator of TeX) is an Emacs user. Hint:
http://www-cs-faculty.stanford.edu/~knuth/programs.html See that
Fvwm2-config and its screenshot. - Eric "ESR" Steven Raymond is an Emacs user. Hints: Author of "Learning
GNU Emacs". See also this: http://www.catb.org/~esr/fvwm2/ - Larry Wall (creator of Perl) is NOT an Emacs user. Hint: His geek
code for Emacs (http://www.wall.org/~larry/ungeek.html) decodes as: "I
refuse to categorize myself on Emacs. Emacs? I don't even know what
that is..." - Tim O'Reilly is NOT emacs user. He uses vi:
http://www.oreilly.com/pub/a/oreilly/ask_tim/1999/unix_editor.html - W. Richard Stevens (RIP) was NOT Emacs user. He used vi. Hints:
- Paul Graham, author of several Lisp books, designer of Arc, founder
of Viaweb (which became Yahoo! Store), ironically uses vi and NOT
Emacs according to http://developers.slashdot.org/comments.pl?sid=117761&cid=9966507 . More proofs needed.
9. Study reflections: 21:12
Similarly, kanji study passes don't take that much time and I absorb things well after a few passes, so I don't have to formally break things up into smaller sets. Here's how I currently do things:
- 1. Write cards for the chapter.
- 2. Do one pass of writing immediately after.
- 3. Do another pass just through the mistakes until I'm happy with them.
- 4. Do another pass through the chapter kanji.
- 5. If I made any mistakes, go back to step 3. If not, put the deck
away for a while.
I have problems remembering the readings now, though, so I should probably go back to doing reading first.
Wow. I'm done with my homework, and it's only 9:08! I have some time to focus on my JLPT-specific review.
10. Time division: 21:25
11. Linux certification: 22:48
Sacha, we can have another one for March - no problem! Just get 14 other people to take the exam with you. :D
Yay! Can people wait for me? =)
I'd love to hear about any questions, comments, suggestions or links that you might have. Your comments will not be posted on this website immediately, but will be e-mailed to me first. You can use this form to get in touch with me, or e-mail me at sacha@sachachua.com .