Emacspeak discussion list

["T.V Raman" <raman AT google.com>]

1. +1 on learning the org bits;
2. See the emacspeak blog article on taking smart notes.
3. What exactly do you mean by "folding" -- there are multiple ways of
   doing that.
4. Good to know you hate the experience, but pointless you saying say
   so without saying why you "hate" it.
5. In general, it's not worth hating things --- at least in your tools,
   use what works for you, ignore the rest.
6. See the blog articles I posted over the  holidays.
7. Read "How to ask questions the smart way" by ESR --it'll make a
   difference to the responses you generate.
8. Use emacs' xref and eglot integration to advantage
9. Chase down the author of the code and see if they have a design-doc.
10. If they dont, then write one as you understand their code, it'll
    help the project as well as you.
11. Depending on the language, exercise your understanding by writing tests.
12. All of the above are good software engineering practice; emacs is a
    tool that helps you do those well --- or poorly depending on how
    well you know to use your tools.

    
--