layout: true name: titleslide class: center, middle
.footnote[ ###
@schmonz
####
#lascot
[schmonz.com/talk
/2018-edinburgh](https://schmonz.com/talk/2018-edinburgh/) ] --- layout: true name: footnotelinks .left-column[
] .footnote[ ###
@schmonz
####
#lascot
[schmonz.com/talk
/2018-edinburgh](https://schmonz.com/talk/2018-edinburgh/) ] --- template: titleslide # Programming
For Non-Programmers
## Amitai Schleier ### 2018/08/14 ??? 1. Press 'C' to clone and move it to projector 2. Press 'P' to show these here presenter notes ### Presenter notes would go here --- layout: false template: footnotelinks .right-column[ # Goals For This Session ## 1. Try _Test-Driven Development_ ## 2. Try _Mob Programming_ ## 3. Collect learnings ] --- .right-column[ # 0. Code of Conduct ## Is there one for this meetup? ## Remind ourselves how we want to behave ## Like TDD, declaring our intentions helps us live up to them ] --- .right-column[ # 1. Try _Test-Driven Development_ (1/2) ## "Tests" on the left ## "Code" on the right ## Let's write a story ## I'll start us off with a test ] --- .right-column[ # 1. Try _Test-Driven Development_ (2/2) ## What we wrote
] --- .right-column[ # 2. Try _Mob Programming_ (1/2) ## Everyone ## Same problem ## Same computer ## Think out loud, together ## Driver, Navigator, rotate ] --- .right-column[ # 2. Try _Mob Programming_ (2/2) ## The FizzBuzz game ## Say goodbye to these slides! ## [cyber-dojo.org](http://www.cyber-dojo.org/kata/edit/5Mwk5WpGFz?avatar=bear) ] --- .right-column[ # 3. Collect learnings - Fun, human, logical, collaborative, not scary - The TDD story helped introduce how we'd be coding - Errors were caught quickly because others were paying attention - Deciding what to do next is an art, and this is humanizing to see - Realistic: we got errors and searched Stack Overflow - Principles apply equally here and in enterprise - Human performance (maintainability) almost always matters more than machine performance - Accomodated both hands-on and observing learners - Visualize what we expect, what we got, what to do - Same process for these notes: write something small, check for correctness - Thin vertical slicing: solving a small part of the problem completely - Keep tests simple, so we don't need to test _those_ too - Mob Programming as a team practice ] --- .right-column[ # References -
Results from the first TDD For Non-Programmers
(twitter.com) -
Results from a recent one
(twitter.com) -
Ivan Sanchez's writeup
(twitter.com) - [Zach Bonaker's detailed writeup](https://web.archive.org/web/20230321132408/https://agileoutloud.wordpress.com/2018/05/11/tdd-by-storywriting/) (wordpress.com) - [Mob Programming Guidebook](https://leanpub.com/mobprogrammingguidebook) (leanpub.com) -
Why I do "Programming For Non-Programmers"
(schmonz.com) -
Coding Tour Summer 2018
(schmonz.com) ] --- .right-column[ # Agile in 3 Minutes ##
agilein3minut.es
> "Before Agile in 3 Minutes, I couldn't get my team to have a > conversation about important topics. Now I have to timebox it."
-
8: Care
-
32: Mob
] --- .right-column[ # Agile in 3 Minutes: The Book ## [leanpub.com/agilein3minutes
/c/lae18](https://leanpub.com/agilein3minutes/c/lae18) The simplest _essays_ that could possibly work. Lowest allowable price on Leanpub, today! ] --- .right-column[ # Let's Keep Going ## [announce-subscribe@schmonz.com](mailto:announce-subscribe@schmonz.com) - Tonight's slides - Upcoming talks - New podcasts - Blog posts ] --- template: titleslide # Programming
For Non-Programmers
## Amitai Schleier ## [latentagility.com](https://latentagility.com)