Skip to content
This repository was archived by the owner on Jun 19, 2022. It is now read-only.

day-5.md

Latest commit

 

History

History
134 lines (110 loc) · 4.21 KB

day-5.md

File metadata and controls

134 lines (110 loc) · 4.21 KB

Day 5

13. Oct. 9:00 - 18:00

  • What do you want to achieve?
  • How would you like to achieve it?
  • What is the first step which you would work on?

Questions

  • What is the difference between Python3 and Python2?
  • How to do object oriented programming (OOP), what is good OOP design?
  • What can we do with numpy/plotting?
  • How to set-up a python project (how to set up modules, init scripts, ...)
  • What is unit testing and what are the best pratices?

Useful links:

Pycon 2013 talk ("Transforming Code into Beautiful, Idiomatic Python"): video: https://www.youtube.com/watch?feature=player_embedded&v=OSGv2VnC0go text content: https://gist.github.com/JeffPaine/6213790

Feedback from Day 1 and Implications for Day 5

(1) I like

  • it was experimental
  • we could learn fomr eachother
  • see where other people are
  • topics
  • different skills, picked up all, could work
  • many guided tutorials, good starting point

(2) I learned/take home

  • ideas, how to analyze
  • Github klowledge, Gitlab
  • culture of writing elegant code
  • details: git, collaboration
  • new things
  • github + using it

(3) I would like to improve

  • collaboration (soul)
    • finding a common point
    • interactivity
    • collaboration
    • small collaboration tasks, Python
    • group examples in small groups
    • collabration process
  • structure (form)
    • slides to start into a topic for building a common ground and knowledge base
    • given tasks
      guidance
      common tasks
    • orinetation/structure
  • content (content)
    • tutorials can be done at home
    • share code, suggest changes, code review + code review tools

(4) Future Actions

Out of point 3, we formulate actions which achieve the needs behind the improvement ideas

  • structure and orintation
    • needs: clarity, efficiency
      • introducing each topic with slides instead of just talking can build a common ground and orient the group
    • needs: group coherence, trust
      • common tasks will help the group to know eachother better, undestand and practice together They can be used in setting where collabration also strengthens the bond between the participants.
        • Forms:
          • Pair Programming
          • Discussions
          • changing roles and feedback
  • Collaboration:
    • needs: connection
      • to get a connection, people need to see eachother as the humans they are and not be defined by their work.
        • Forms:
          • valuing athmosphere of acceptance
          • meet at lunch together, discuss about what you do outside of the GeoX
          • have a after school chill out somewhere
    • needs: help
      • to reduce the hurdle to ask other people for, we can have them collaborate and talk right away.
        Forms:
  • Content:
    • Motivation: Why use Python
    • One Algorithm in Python, Matlab, R, C.
      • Idea: find ways to express the same program, relate to known language
      • Not Idea: Compare the languages on a metric
    • Python:
      • How to write modules
      • How to do OOP (Python Tutor) self, __init__, attributes
      • Coding practice and guidelines (Hound CI)
      • image processing (Nicco does not do that so needs to ask someone help)
      • how to use numpy
      • debugging and stepping though

(5) Building Blocks

Each of the building blocks addresses one or more of the needs and forms from above. It is estimated in time, particpant number and content.

Nicco proposes to prepare the following. If you think something is missing, please open an issue and consider preparing it yourself as it is important to you.

Forms:

Tools: