Workflow Concepts
To Make Everyone Happy
Who is this nobody?
Problem Solver
Tod Hansmann
- Dev Culture and Workflow Consultancy/Contractors
- Dedicated to Open Source
- Old Man yelling at Sky
- Seen some things
- The Impossible is Easy! (Sometimes.)
# CHAPTER 2
Two Core Principles
- Tight Feedback Loops
- Decoupling Thinking through Automation
# CHAPTER 2
Principles
- Git is the Workflow
- Deploy First
- Care About Less Things
Git is the Workflow
- git clone
- git checkout -b my-branch
- work
- git commit, go back to 3 until done
- git push
- make PR
- approval from someone else (hopefully)
- merge to trunk, git checkout trunk, go back to 2
Deploy First
We make poor assumptions about environment
Deploy everywhere from the beginning, including locally
Now we have no assumptions that get in the way
No, there are no exceptions to this
Care About Less Things
Things your code should not care about:
- What is the environment? Prod? Nonprod? Laptops?
- Where do logs go? (Rant about logs another time)
- What is my domain/path?
- Which of N am I? (Isolate state)
- What am I running on? Kubernetes? Jetbrains?
- Dependency coupling! (URL and API Contract only)
- I want behavior, not configuration. (I don't care about networking, I care about connectivity, the platform cares about networking.)
Questions?
Find me after, or @TodPunk or THansmann just about everywhere
Workflow Concepts
By Tod Hansmann
