veyepar: Software Engineering For Beginners: A Jr. Developer's Guide

Author(s):	Kojo Idrissa
Location	Cartoon 1
Date	jul Sat 28	Days Raw Files
Start	14:00	First Raw Start	13:43
Duration	0:45:0	Offset	0:16:09
End	14:45	Last Raw End	15:13
Chapters	00:00 0:13:43 0:43:43
Total cuts_time	45 min.

https://pyohio.org/2018/schedule/presentation/8/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Software_Engineering_For_Beginners_A_Jr_Developers_Guide.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

# An Outline of the Talk

# Version Control (Git)
-  Why
    *  Protect yourself from mistakes
    *  Enable yourself to take chances & try new things
    *  Learning to work w/ a team

#  When?
*  10 or more lines of working code that you're scared to change because it might break

#  What/How
*  Basic feature branch/merge workflow

#  Reference: Pro Git Chapters [1-3](https://git-scm.com/book/en/v2)

# Documentation

#  In Code vs About Code: Start w/ In Code

#  Why
*  Help your future self
*  Help your teammates help you
*  Avoid that form of technical debt

#  When
*  Writing code using a new technique
*  Writing functions, especially if they call other functions

#  How
*  Docstrings for functions (minimums)
    -  What the function does
    -  What it takes as input (include data type)
    -  What it produces as output (include data type)

#  Next Step: Learn about ReStructured Text and/or Sphinx for general documentation

# Testing & TDD
##  Testing vs "PURE" TDD
##  Why
*  Tests protect you from future changes breaking things
*  TDD: "write tests first" forces you to think before you type

##  When
*  As soon as possible
*  Art + Science: experience helps

##  How
*  New coders: Python unittest and doctests
*  Experienced coders: pytest

##  Next Step
*  New coders: pytest
*  Experienced coders: Continuous Integration

# Other
##  Dependency Management/Deployment
*  VMs
*  Containers
*  Virtual Env

##  Development Environment
*  CLI vs. GUI
*  Linux/Unix/Windows/OS X

Comment:

production notes