---
# System prepended metadata

title: Thursday 11b

---

# Thursday 11b
[toc]

## WEEK_1
**"How many hours of zoom calls happen everyday (on average)?**
### GROUP_1 AERO 
- GROUP AERO DA BEST <3
- 10 milly

### GROUP_2 BLINKER
15 million


### GROUP_3 CACTUS
- 300 million ## U R OUTLIERED



### GROUP_4 DORITO
- 53.1415926535897932384626433832795 million :)


### GROUP_5 ECHO
- 30 million- calls per day
- average of 2-3 hours per call
- 60-90 million hours


### our clas answer
- 34.5 Millions hrs in my bank acc


## WEEK_2
First Name must be at least 3 characters, and no more than 30.
Last Name must be at least 3 characters, and no more than 50.
First Name can only contain letters (uppercase or lowercase), and dashes.
Last Name can only contain letters (uppercase or lowercase), spaces, and dashes.
Middle Name can be None, but if it's not none, it can be between 1 and 50 characters.
Middle Name cannot be longer than the first name, and it cannot be longer than the last name.
### GROUP_1 AERO
GROUP AERO DA BEST <3
copyright © group aero 2021 
| Input | output |
| -| - |
| len(firstname) < 3 characters | false |
| len(firstname) > 30 | false |
| len(lastname) < 3 | false |
| len(lastname) > 50 | false |
| firstname.isalpha() | true |
| firstname.contains("-") | true |
| lastname.isalpha() | true |
| lastname.contains("-") and lastname.contains(" ") | true |
| len(middle_name) > 50 | false |
| len(middle_name) > len(firstname) | false |
| len(middle_name) > len(lastname) | false |


### GROUP_2 BLINKER
|Input | Output |
|---|---|
|len(firstname) < 3| False|
|len(firstname) > 30|False|
|len(lastname) < 3 |False|
|len(lastname) > 50|False|
|len(middlename) > 50 |False|
|len(middlename) > len(firstname) |False|
|len(middlename)>len(lastname) | False|
|lastname.isalpha()|True|
|firstname.isalpha()|True|


### GROUP_3 CACTUS

| Input | Output |
| -------- | -------- | 
| len(firstname) < 3 | false    | 
| len(lastname) < 3 | false | 
| len(firstname) > 30 | false | 
| len(lastname) > 50 | false | 
| len(middlename) > 50 | false |
| len(middlename) > len(firstname) | false | 
| len(middlename) > len(lastname) | false | 
| firstname.isalpha() or  | -------- |


### GROUP_4 DORITO
| Input | Output |
|--|--| 
| len(firstname) < 3| False |
| len(lastname) < 3 | False | 
| len(firstname) > 30 | False | 
| len(lastname) > 50 | False |
| len(middlename) > 50 | False |
| len(middlename) > len(firstname) | False | 
| len(middlename) > len(lastname) | False |
| firstname.isalpha() | True |
| lastname.isalpha() | True |

### GROUP_5 ECHO
| Input | Output |
|-------|--------|
|len(firstname) < 3|False|
|len(firstname) > 30|False|
|len(firstname) >= 3 and len(firstname) <= 30|True|
|len(lastname) < 3|FALSE|
|len(lastname) > 50| FALSE|
|len(lastname) >= 3 and len(lastname) <= 50|TRUE
|len(middlename) > 30|False|
|len(middlename) < 1|False|
|len(middlename) >

## WEEK_3
Each group in the tutorial should share a summary of their teams plans and progress in relation to:

* When (or if) they are running standups and whether they are synchronous or asynchronous
* How often they meet, how they meet, and what the goals/outcomes of any meetings so far have been
* Have they or will they try pair programming
* Any challenges they've faced already after being in a group for a week

Other group members (in other teams) are encouraged to ask questions and learn from what other groups are doing/saying.
### GROUP_1 AERO
- Group AERO the best
- Meeting 3-4 times a week!
- Standups occuring for approx 20 mintues occuring synchronously 
- We have done pair programming
- No challenges because we are the best and do nothing wrong
- but we've done quadruple programming lol


### GROUP_2 BLINKER
- Three times a week through zoom/teams, we chat  everyday if we have issues to be clarified
- The process is synchronous
- We are doing pair programming also tri-programming
- Challenges - we haven't decided our data structure T^T 
             - importing stuff  from diff directory
             - what assumptions to make
- sometimes theres conflict on git

### GROUP_3 CACTUS
- Frequent meet ups of around 3 times a week on discord (2-3 hrs) 
- Have done group programing together for more difficult functions
- Challenges, our codes dont work and alot of confusion

### GROUP_4 DORITO
- Having frequent meetings (2/3 times per week)- average length of 1 hour
    - Goals of the meetings are progress monitoring and assigning of new roles
- Have tried pair programming
- Challenging to organise a meeting for everyone to attend
- Daily messaging

### GROUP_5 ECHO
- Frequent meetings (2-3) times per week through Teams
- Talking daily (on messenger) about any issues
- Constant peer review of eachother's code
- No standup so far: will try later
- haven't tried pair programming
- Goal: understanding what the tasks are about
- challenges: confusion with the tasks - not sure what the output should look like (for testing)


## WEEK_4
```python
def check_password(password):
    
    if password == "password" or password == "iloveyou" or password == "123456":
        return "Horrible password"
    elif (len(password) >= 12 and any(x.isupper() for x in password) and
        any(x.isdigit() for x in password) and 
        any(x.islower() for x in password)):
        return "Strong password"
    elif len(password) >= 8 and any(x.isdigit() for x in password):
        return "Moderate password"
    else:
        return "Poor password"
   
if __name__ == '__main__':
    print(check_password("ihearttrimesters"))
    # What does this do? 

```

```python
def check_password(password):
    '''
    Takes in a password, and returns a string based on the strength of that password.

    The returned value should be:
    * "Strong password", if at least 12 characters, contains at least one number, at least one uppercase letter, at least one lowercase letter.
    * "Moderate password", if at least 8 characters, contains at least one number.
    * "Poor password", for anything else
    * "Horrible password", if the user enters "password", "iloveyou", or "123456"
    '''
    horrible_pw = ["password", "iloveyou", "123456"]
    digit = False
    upper = False

    if password in horrible_pw:
        return "Horrible Password"
    elif len(password) >= 8:
        for char in password:
            if char.isdigit():
                digit = True
            elif char.isupper():
                upper = True
        if digit and upper and len(password) >= 12:
            return "Strong Password"
        elif digit:
            return "Moderate Password"
    
    return "Poor Password"

if __name__ == '__main__':
    print(check_password("ihearttrimesters"))
    # What does this do?
```

Compare these two pieces of code from a pythonic, style, and readability point of view and choose which one you prefer. When you choose one, you must justify your reasoning in the shared document your tutor gives you.
### GROUP_1 AERO
The second code contains a docstring which explains clearly what the function does
while there are more lines in the second code, the if functions are clearer with well defined variables




second code is more readable
### GROUP_2 BLINKER
The second code includes a docstring which clearly describe what the function does with different scenarios
The if statements in the first code example are messy and hard to understand
The first code does not have a docstring describing what the function does
The second code has a much clearer variable names
The second code has less code and is more organised e.g putting horrible passwords in a list


### GROUP_3 CACTUS
First code has very long lines compared to the second one making it hard to understand what each line means.    
Second has docstrings.
Second is more readable compared to first.

### GROUP_4 DORITO
- Second one has nice docstrings, the first one has none.
- Large conditional statements, if this and this and this,
   elif this and this and this, its not very nice.
- isupper and islower can work on strings too. Should check password.islower() == False (not all of the password is lowercase therefore at least                       one character is uppercase. works with numbers in the string too)
- First code uses varibale name "x" which isn't great


### GROUP_5 ECHO
- Second one is shorter
- First one does not have docstrings
- the if .. in .. makes it clearer what we are checking for
- horrible password was in a list (consice)
- the second version can be shorter if it uses the any function


### Together
Q. What are attributes of good requirements?
- Clear and concise statement for what you want to accomplish
- Understandable, proper grammar 
- Achievable, singular + focus 1 story.
- Testable

Q. How could we clean this up into well described requirements? 
"I want a burger with lots of pickles and mayo but I need to make sure that the mayo doesn't make the burger bun really wet. Oh, and it needs to be warm, like, made less than 5 minutes ago warm but not so hot that I burn myself. I'm also not a big fan of plastic containers so if it could be in a paper bag that would be good. Actually, make that a brown paper bag, I like the colour of that"

Requirements
- User should be given a medium size burger.
- Burger should have 5 pickles
- Burger should have 2 table spoons of mayo
- Burger should not be wet
- Burger should delivered within 5 mins of making 
- Burger should delivered warm
- Burger should be delivered in a brown paper bag



## WEEK_8
### GROUP_2 BLINKER
- url/message(dm)/send/photo
* Inputs: token, channel_id/dm_id, url of the photo 
* Methods: POST
- url/message(dm)/reaction
* Inputs: token, channel_id, message_id, 
* Methods: POST
- url/message/disappearing/meassages
* Inputs: token, channel_id, time for disappearing
* METHODs: 
- url/messages/poll
* Inputs: token, channle_id, title, options
- url/user/setnickname
- url/user/profile_picture/upload
- url/screen/share
- url/screen/remote/control
### GROUP_3 CACTUS
- url/user/mute/
- Takes in a valid token and u_id of a user. Mutes the user for given time. Adds user to a new list in data(called muted_list) until time is up.
- Inputs: token, u_id, time
- POST
- returns
- url/user/addprofilepic/
- Inputs: Token, jpeg
- Adds picture to user. can be viewed with user/profile/
- POST
- returns: {}
### GROUP_4 DORITO
- usr/block
    - token, user_id
- channel/mute turns off notifications
    - token, channel_id
- usr/profile/about_me
    - token, description 
- usr/profile/other_socials
    - token, platform ()
- games integration: farmville, community snake, chess
- bots for announcements, music,  
- 
### GROUP_5 ECHO
- message/send/photo, message/sentdm/photo
- send photo to the channel/dm
- Inputs: token, channel_id/dm_id, photo_url
- POST
- returns {message_id}



#### DONT TOUCH
## WEEK_TEMPLATE
### GROUP_1 AERO
### GROUP_2 BLINKER
### GROUP_3 CACTUS
### GROUP_4 DORITO
### GROUP_5 ECHO
