Thursday, April 23, 2020

Dos and Don'ts in Academic Presentation


Before reading this article it is suggested to read the previous article on 201 presentation skills (in Bahasa, right-click in Chrome and click translate, to make it in English).

This article is a resume/summary of the book "Conferencing and Presentation" by Michael Guest, particularly on Part IV (chapter 12-16). The book itself is free and can be downloaded from the Springer  Nature website. The following dos and don'ts focus on a practical manner from opening to closing. Before entering this structure, however, formulae to formulaic academic phrases serve is listed as building blocks of academic discourse. These formulae including,
  1. Occupy a mid-point between ‘general English’ and specialist terminology;
  2. Contain constituents that are flexible (i.e., excluded vs. ruled out, possibilities vs. results);
  3. Have cross-disciplinary academic application;
  4. Are utilized in both written and spoken modes;
  5. Hold long-term (intrinsic) value for academics/professionals;
  6. Mark entry or membership into the academic discourse community.
Having those formulaic phrases, Let's start the practical implementation of those phrases in the academic presentation.

1. Opening
Don'ts:
  • My name is X, and my presentation is entitled Y. (this and next three are too slight)
  • Hello everyone.
  • My topic today is X. (This and below are too much casual)
  • Today I’m going to present about X.
  • I’ll present on X, OK?
  • OK, so, I’ve just changed the title to show... X.
  • I’m gonna talk about something that is very hot ‘n sexy...

Monday, April 06, 2020

Berpindah ke vscode (dari gEdit)

Hidup itu harus dinamis, tidak harus saklek pada satu hal (tool/perangkat). Ketika ada perangkat lain yang lebih mudah, meskipun awalnya saya membencinya, maka kita harus berpindah ketika ternyata perangkat tersebut memberikan kemudahan dan kecepatan dari perangkat lama.

Kali ini saya berbicara tentang "editor", perangkat lunak yang digunakan untuk mengetik. Contoh editor sederhana adalah notepad di Windows. Di Linux, sejak pertama kali menggunakannya secara intensif tahun 2009 sampai sekarang, editor bawaan dari Gnome, yakni gEdit, adalah editor default saya, selain vim. Dua hal utama yang saya gunakan dengan editor: (1) mengkoding Python, dan (2) membuat manuskrip dengan Latex. Hal-hal lainnya adalah menulis dengan markdown, txt, dan format-format lainnya. Jadi, editor yang saya gunakan paling tidak harus mendukung Python dan Latex, dan gEdit sudah mendukung keduanya dengan beberapa kekurangan (code completion, snippets, dll).

Setelah mencoba beberapa editor lain: Atom, Sublime text, Spyder, PyCharm, dan vscode, akhirnya saya memutuskan vscode sebagai editor saya untuk seterusnya. Tulisan ini mengupas kenapa saya berpindah dari gEdit ke vscode.


Related Posts Plugin for WordPress, Blogger...