defensive programming lesson as written takes a big leap from the previous lessons; the normalize_rectangle and range_overlap code would be tough for beginners to jump into. Maybe instead of starting with that tough new code we could throw some "assert" commands into their run_analysis function (for the inflammation data) to make sure the loaded datasets have the correct number of lines.
and
lesson going back to simpler code (maybe the temperature functions) would be helpful.
The text was updated successfully, but these errors were encountered:
I think this is a good idea, but I'm not sure what sort of example we might use instead. Any ideas? If possible it would be good to link back to the inflammation narrative.
At last debriefing session someone mention that
and
The text was updated successfully, but these errors were encountered: