search

swkWien / sessions

Session presentations for Coding Dojo Vienna
http://swkwien.github.io/
16 stars 7 forks source link

GDCR23: Program and Sessions #113

Closed caichinger closed 1 year ago

caichinger commented 1 year ago

Result should be documented here: https://github.com/swkWien/sessions/blob/master/2023/cr20231104_gdrc/sessions.md

Topic: Different TDD Styles

Tag line: Focus on different TDD styles to facilitate test-first development

Target audience

Diverse, should be doable for beginners but provide enough challenge/room for experienced developers as well, e.g. through optional constraints

Kata: Tetris

Tetris from the ground up.

Description: TODO

Links:

Sessions

  1. Pen & Paper (Skizze machen, UML, C1-C4; ev. Testlist, etc.)
  2. Inside Out (TDD, Pair Programming; Detroit/Chicago; ev. Demo, mit bisschen Design up front)
  3. Outside In (mit Fakes oder Mocks; London)

Lunch

  1. TDD as if you meant it (ist Inside Out, no Design up front, emergent, -> refactoring
  2. Outside In (Extreme fake it till you make it, Munich)
  3. Ensemble/verrücktes Constraint/freies Constraint ()

See also

See also https://picostitch.com/blog/2017/11/25-jscoderetreat-12/

gregorriegler commented 1 year ago

I'm happy to help with facilitation.

codecop commented 1 year ago

https://youtu.be/_S5iUf0ANyQ?si=9sYe7hu0ZvIt7AI9

caichinger commented 1 year ago

Picking up the idea from our discussion, I think it would be useful to introduce each style with a very brief demo at the beginning of the corresponding session. To this end it would be nice to have a suitable example at hand where we can showcase the different approaches. Maybe we can think of something until our next meeting.

caichinger commented 1 year ago

Given the discussion we had last week, I believe one of the challenges with doing the Kata outside-in is identifying suitable collaborators. I guess that is often a challenge but in the Kata the collaborator is maybe not another obvious actor/system but rather an abstraction within the game/domain; for example the bottom/pile that @maosmurf and @codecop used in their approach.

Pile = all pieces that have already descended and settled on the floor/bottom of the game

Typical_Tetris_Game svg

(The pieces in the grey box; not the bounding box ;)

ReaSu commented 1 year ago

Sessions from https://github.com/swkWien/sessions/issues/111

  1. @caichinger pen & paper

  2. @ReaSu Focus: Pair programming & Ping Pong; Test first; Test least ("Inside out")

    Demo Fizzbuzz @caichinger & @ReaSu: was heißt Test first? Was heißt Ping Pong

  3. @gregorriegler "Outside in" without mocks

  4. @maosmurf Outside in with predefined interface to be mocked

  5. @rolger presents a selection of constraints (@gregorriegler 1x ensemble session @ different room)

ReaSu commented 1 year ago

@maosmurf session 4: Wie stellen wir sicher, dass alle wissen, was ein Mock ist? Brauchen wir ein Interface - wenn ja, in welchen Sprachen? Ist das Ziel, dass alle ein Mockingframework verwenden?

@rolger hat eine Trainingssession, die als Grundlage dienen könnte?

caichinger commented 1 year ago

In diesem Issue bitte nur mehr Beiträge zum Programm in seiner Gesamtheit.

Etwaige Detailabstimmungen in den jeweiligen Issues:

Zur Erinnerung (danke Rea;), unser diesjähriges Motto/Thema: Explore different TDD Styles, i.e. strategies to facilitate test-driven development

Verantwortlichkeiten als Facilitator:

caichinger commented 1 year ago

Wenn ihr der Meinung seid, dass ihr mehr/weniger Zeit braucht, bitte melden.

Der Zeitplan ist mehr oder weniger übernommen vom letzten Jahr.

caichinger commented 1 year ago

Die Slides sind jetzt public. :partying_face: