1/3
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai |
|---|
No analytics yet
Send a link to your students to track their progress
assignment tips
for every function you must write a docket string to explain what the function does
variables must be named by like actual names and should be lowercase and use underscores for multiple words
each line must be less than 100 characters, and u musts be use a back slash to break lines if you have more than 100 characters
you can use # for in-line comments to clarify confusing parts of code
For task 6, you’ll have to use f-string substitution and also use spacing/justification thing
- e.g. f”First number is {x:<5}“
The general rule of thumb that we use with comments is if a colleague can look at your code and understand what it does in 5 sec, then it probably doesn't need a comment. Otherwise, add a comment in! The purpose of a comment is to explain what your code is doing. If you think it might be unclear, then add a comment!
String slicing format
string[start : end : step]
a