Lambdas, Streams and Events
See csse2002 for course logistics.
Lambdas are examinable; event-driven programming and GUIs are not — confirmed in 2026-05-28-course-summary-and-exam-preparation. The two halves carry very different revision weight.
Topics
- Lambdas in Java — anonymous functions, scope, and the functional interfaces that give them a type. Examples: an anonymous function in JS, in Python and in Java; what a lambda captures from its enclosing scope; filtering with a
Predicate. - Streams in Java — a basic
.stream()example, then one worked pipeline, built up one line at a time. - Events — including how to make your own toy event system.
- An anecdotal survey of QLD dev teams (see below).
All the technical content lives in java-lambdas-and-streams and java-events.
Events
Using an event API is easy to pick up. It is often the first design pattern people use at high school, wiring up buttons on a website, without realising it. Two things are not picked up naturally:
- a basic, naive event system implementation, which shows what is going on under the hood;
- a variant of the CSSE2002 game engine (the engine used in the assignments) with an event system integrated, which shows how much “connective tissue” code it removes.
Both are written up in java-events.
Applied class
See week11-tutorial-dependency-inversion — more practice with Dependency Inversion, extending java-solid-principles (Week 7).
Aside: anecdotal local industry survey
An informal, anonymised survey of one engineer’s professional network: 14 QLD-based dev teams (13 excluding the surveyor’s own) across 12 distinct organisations. It is not representative data. It reflects only one person’s connections in the dev scene, with no QLD teams in big tech, consultancies or banks. The findings (on AI tool usage and graduate hiring) are not course content.