Loading README.md +17 −16 Original line number Diff line number Diff line Loading @@ -19,27 +19,28 @@ Universität Hohenheim, Wollgrasweg 43, Seminarraum S 12 # Introduction Modellierungs-Fitnessclub is a monthly meeting where researchers talk about how they build modelling workflows with coding harnesses (such as Claude code, OpenAI Codex, cursor, Open code or Pi). This is a hands on workshop to practice data science skills that are transferable between scientific domains. We are all learning how agentic programming is disrupting software engineering and our modelling work as a result. Modellierungs-Fitnessclub is a hands on meeting where researchers build modelling workflows with coding harnesses (such as Claude code, OpenAI Codex, cursor, Open code or Pi). This is a workshop to practice data science skills transferable between scientific domains. We are all learning how agentic programming is disrupting software engineering and our modelling work as a result. - The 90 minutes meeting is a Hands on workshop on a modelling dataset and associated data analysis tools. In 4 phases: - The 90 minutes workshop chooses and analyses one dataset in 4 phases: 1. 5 minutes. Round of introduction 1 minute per project (with timer). Group decision on the most mature or desirable project among the submitted ones. 1. **Choice Phase** 5 minutes. Round of introduction 1 minute per project (with timer). Group decision on the most mature or desirable project among the submitted ones. 2. 15 minutes specification we discuss on a drawing board or sheet of paper what do we want to achieve in the session. 2. **Specification Phase** 15 minutes. On a drawing board or sheet of paper, we specify what we want to achieve during the session. 3. 1 hour of Implementation with at least one, preferably two or more laptops which load the dataset, tools, and generate software with a coding agent. We push the code to this git repository under a new sub directory corresponding to the day of the event. 3. **Implementation Phase** 1 hour. Implementation with at least one, preferably two or more laptops which load the dataset, tools, and generate software with a coding agent. We push the code to this git repository under a new sub directory corresponding to the day of the event. 4. 10 minutes wrap-up what worked, what didn't work. 4. **Wrap-up Phase** 10 minutes. What failed, what went well, what can we improve next time. - Throughout the specification and implementation phase, we can discuss about visualizations such as histogram, scatter plot, line chart, area chart, bar chart, Loading Loading
README.md +17 −16 Original line number Diff line number Diff line Loading @@ -19,27 +19,28 @@ Universität Hohenheim, Wollgrasweg 43, Seminarraum S 12 # Introduction Modellierungs-Fitnessclub is a monthly meeting where researchers talk about how they build modelling workflows with coding harnesses (such as Claude code, OpenAI Codex, cursor, Open code or Pi). This is a hands on workshop to practice data science skills that are transferable between scientific domains. We are all learning how agentic programming is disrupting software engineering and our modelling work as a result. Modellierungs-Fitnessclub is a hands on meeting where researchers build modelling workflows with coding harnesses (such as Claude code, OpenAI Codex, cursor, Open code or Pi). This is a workshop to practice data science skills transferable between scientific domains. We are all learning how agentic programming is disrupting software engineering and our modelling work as a result. - The 90 minutes meeting is a Hands on workshop on a modelling dataset and associated data analysis tools. In 4 phases: - The 90 minutes workshop chooses and analyses one dataset in 4 phases: 1. 5 minutes. Round of introduction 1 minute per project (with timer). Group decision on the most mature or desirable project among the submitted ones. 1. **Choice Phase** 5 minutes. Round of introduction 1 minute per project (with timer). Group decision on the most mature or desirable project among the submitted ones. 2. 15 minutes specification we discuss on a drawing board or sheet of paper what do we want to achieve in the session. 2. **Specification Phase** 15 minutes. On a drawing board or sheet of paper, we specify what we want to achieve during the session. 3. 1 hour of Implementation with at least one, preferably two or more laptops which load the dataset, tools, and generate software with a coding agent. We push the code to this git repository under a new sub directory corresponding to the day of the event. 3. **Implementation Phase** 1 hour. Implementation with at least one, preferably two or more laptops which load the dataset, tools, and generate software with a coding agent. We push the code to this git repository under a new sub directory corresponding to the day of the event. 4. 10 minutes wrap-up what worked, what didn't work. 4. **Wrap-up Phase** 10 minutes. What failed, what went well, what can we improve next time. - Throughout the specification and implementation phase, we can discuss about visualizations such as histogram, scatter plot, line chart, area chart, bar chart, Loading