It:s that time of year again. We got the results for the Faculty Development questionnaires handed out to students in our classrooms. I haven't been programming much, but I think reading the Pollen docs, aoc-racket, and some of the scribble documentation code is helping re-write scripts for readability. During the “make-it-work” stage I get so busy reading documentation and on-line pages (stackoverflow always seems to have a discussion that helps). The re-discovery of Perl Best Practices and a quick reading of the chapter about naming variables is helping too: the general idea of naming variables so that they structure reads smoothly when you use them later.
If I can figure out how to give each plot-pict a name, I'll be able to use pin-over and rt-find to annotate questions. For now only the title text is named. With the title pict named inset let me place the response table without relying on coordinates discovered from a bitmap in GIMP.
データ表から意味を取るのが難しいようですが、アンケート結果の視覚化するのが能力開発に繋げることができる。基礎プログラミングとデータ視覚化の授業を作ってから、いろいろな学生(または先生)が自らアンケートを作成と実施、分析できるようになるかもしれない。FDも参加型、 “Nothing About Us Without Us”の理念を行かして 大学の「民衆化」(fn:1) の時代に相応しい動きになります。
The code needs editing, but I like this view of questionnaire data where “factor” responses of 1 and 2 are negative, 3 is seemingly neutral, and 4 and 5 are positive. It seems possible to see things with this view that might not be possible with an average/mean of the responses.
The visualization needs to be on a page with the full text for the questions, the symbols for the numbered responses, the tables for the data, and an attempt to explain the visualization.