The Dart language
Null safety, records, patterns, sealed classes and generics. The parts that change how you design.
7 of 7 written
Flutter and Dart, to senior
The language properly, then the judgement calls a senior interview is actually testing.
Where this stands
39 of 39 lessons written. Every bar below is counted from the lesson files that exist. A planned lesson says so on its own page.
- 110 Dart panels, every one executed by Dart 3.13.1 and analysed with
--fatal-infos - 483 assertions, all passing, or this build would have refused to write
- 26 widget panels, run as real widget tests by
flutter test - 19 panels that deliberately do not compile, each proven to fail with the exact rule named
- 22 shown but not run, each stating why on the panel
- No network at read time. No npm dependencies.
Asynchrony and isolates
Futures, streams, cancellation, backpressure and real concurrency. Where most production bugs live.
6 of 6 written
How Flutter actually draws
The three trees, constraints, keys and the rendering pipeline. The most common senior interview topic.
5 of 5 written
State management
From setState to Bloc and Riverpod, and the question underneath all of them: who owns this state?
5 of 5 written
Architecture
Layers, dependency injection, error modelling and offline. What "architectural thinking" means in an advert.
6 of 6 written
Testing and performance
Unit, widget and golden tests; then finding and fixing jank with evidence rather than guesses.
6 of 6 written
The senior interview
The three things you are actually judged on, and how to answer a mobile system design question.
4 of 4 written