• Finished final bits of 261 which included fixing some bugs I’d created

• some lingering PRs COMPLETE!

• some slightly boring technical details getting ironed out with dependencies etc

• Linted entire codebase. (Migrating to pylint instead of superlinter)

• Refactor of the scraper functions - use a shared payload function in payload.py rather than each having a global dictionary variable.

• Did something this week which is a plus…

• the pace is pretty ok for week 5 - lots of load in the team but we are still getting the important stuff done

• Got a lot more comfortable with where in the codebase many of the things are and the process with which data is retrieved then processed.

• new PRs are lasting a shorter time generally

PACE IS GENERALLY INCREASING! yayyy

• some issues regarding load possibly? Some cards ended up getting blown out because of unforseen issues.

• Parts where things need to be changed / added that Im not 100% comfortable describing the function / class.

• reviews from other team members?

• As you come across functions with missing docstrings, if you work on them and start to understand how they work, you can take the initiative to write a corresponding docstrings.

• For all new functions, ensure that there is an accompanying docstring

•  

• Write tests first, add code, refactor, repeat

• Figure out exactly what needs to be done for 287and then (hopefully) do it

• 273 PR on tuesday, review / merge 1-2 days after.

• 278 PR on Friday

• deployment ???? yes/no?

• get more PRs reviewed by others.

@Peter Derias (Unlicensed) clarify theme for this sprint

@Luke Banicevic (Unlicensed) investigate #274 ????????

 blocking cards:

@Joel West (Unlicensed) @Peter Derias (Unlicensed) are going to be working on this one.

all of these are well on their way to being done.

cards that might be cool to complete before, but not mandatory: