Join us to discuss ten things engineers should learn about learning on Monday 5th February at 2pm GMT

See one, do one, teach one” is a popular technique for teaching surgery to medical students. It has three steps:

  • You see one: by watching it, reading about it or listening to it
  • You do one: by engineering it or making it
  • You teach one: by telling others all about it


If you’re teaching engineers, what do you need to know beyond the seeing and doing? Understanding how human memory and learning works and the differences between beginners and experts can improve your teaching. So what practical steps can engineers take to improve the training and development of other engineers? What do engineers need to know in order to improve their own learning?

Join us on Monday 5th February at 2pm GMT (UTC) for our monthly ACM SIGCSE journal club meetup on zoom to discuss a paper on this topic by Neil Brown, Felienne Hermans and Lauren Margulieux, published in (and featured on the cover of) the January issue of Communications of the ACM. [1]

We’ll be joined by the lead author, Neil Brown of King’s College London, who will give us a lightning talk summary of the paper to kick off our discussion.

All welcome, as usual, we’ll be meeting on zoom, details at sigcse.cs.manchester.ac.uk/join-us

References

  1. Neil C.C. Brown, Felienne F.J. Hermans and Lauren Margulieux (2024) 10 Things Software Developers Should Learn about Learning, Communications of the ACM, Volume 67, No. 1. DOI:10.1145/3584859 (see accompanying video at vimeo.com/885743448 )

Join us to discuss novice use of Java on Monday 7th November at 2pm GMT

Java is widely used as a teaching language in Universities around the world, but what wider problems does it present for novice programmers? Join us to discuss via a paper published in TOCE by Neil Brown, Pierre Weill-Tessier, Maksymilian Sekula, Alexandra-Lucia Costache and Michael Kölling. [1] From the abstract:

Objectives: Java is a popular programming language for use in computing education, but it is difficult to get a wide picture of the issues that it presents for novices, and most studies look only at the types or frequency of errors. In this observational study we aim to learn how novices use different features of the Java language. Participants: Users of the BlueJ development environment have been invited to opt-in to anonymously record their activity data for the past eight years. This dataset is called Blackbox, which was used as the basis for this study. BlueJ users are mostly novice programmers, predominantly male, with a median age of 16. Our data subset featured approximately 225,000 participants from around the world. Study Methods: We performed a secondary data analysis that used data from the Blackbox dataset. We examined over 320,000 Java projects collected over the course of eight years, and used source code analysis to investigate the prevalence of various specifically-selected Java programming usage patterns. As this was an observational study without specific hypotheses, we did not use significance tests; instead we present the results themselves with commentary, having applied seasonal trend decomposition to the data. Findings: We found many long-term trends in the data over the course of the eight years, most of which were monotonic. There was a notable reduction in the use of the main method (common in Java but unnecessary in BlueJ), and a general reduction in the complexity of the projects. We find that there are only a small number of frequently used types: int, String, double and boolean, but also a wide range of other infrequently used types. Conclusions: We find that programming usage patterns gradually change over a long period of time (a period where the Java language was not seeing major changes), once seasonal patterns are accounted for. Any changes are likely driven by instructors and the changing demographics of programming novices. The novices use a relatively restricted subset of Java, which implies that designers of languages specifically targeted at novices can satisfy their needs with a smaller set of language constructs and features. We provide detailed recommendations for the designers of educational programming languages and supporting development tools.

All welcome, as usual we’ll be meeting on zoom, details at sigcse.cs.manchester.ac.uk/join-us

References

  1. Neil C. C. Brown, Pierre Weill-Tessier, Maksymilian Sekula, Alexandra-Lucia Costache and Michael Kölling (2022) Novice use of the Java programming language ACM Transactions on Computing Education DOI:10.1145/3551393