%author: Gabriel Chaney %date: 2019-06-25
-> What a non-engineer should know about how an engineer thinks. <-
- Scenarios
- Write some code
- Contemplate
- Day 1, 8:05AM - Client sends specs to HosOps: add 1+1 π’
- Day 1, 8:24AM - HosOps gives specs to the Engineer πΎ
- Day 2, 10:39AM - Engineer starts writing code... π»
- Day 10, 11:39PM - ...Engineer tests code and shipsit π’
- Day 11, 8:05AM - HosOps reports good news to Client π
- Day 12, 9:52AM - Client reports that it's working π
- Day 1, 8:05AM - Client sends specs to HosOps: add fifteen 1's π’
- Day 1, 8:24AM - HosOps gives specs to the Engineer πΎ
- Day 2, 10:39AM - Engineer starts writing code... π»
- Day 10, 11:39PM - ...Engineer confidently skips testing and shipsit π’
- Day 11, 8:05AM - HosOps reports good news to Client π
- Day 12, 9:52AM - Client triggers 911 π
-> What's wrong with this picture? <-
-> Readability <-
- Day 12, 10:38AM - Engineer scrambles to apply readability and fix 911 bug... π
- Day 12, 11:39PM - ...Engineer learned her lesson, tests, and shipsit π’
- Day 12, 8:05AM - HosOps reports good news to Client π
- Day 13, 9:52AM - Client reports that it's working π
- Day 1, 8:05AM - Client sends specs to HosOps: add one thousand 1's π’
- Day 1, 8:24AM - HosOps gives specs to the Engineer πΎ
- Day 2, 10:39AM - Engineer starts writing code... π»
-> How do we support multiple clients with similar specs? <-
-> Reusability <-
- Day 4, 11:39PM - ...Engineer refactors code to be reusability for clients 1-3, tests code and shipsit π’
- Day 5, 8:05AM - HosOps reports good news to Client π
- Day 6, 9:52AM - Client reports that it's working π
- Day 1, 8:05AM - Client sends specs to HosOps: if non-zero, add variable number of 1's. else, return 1 π’
- Day 1, 8:24AM - HosOps gives specs to the Engineer πΎ
- Day 2, 10:39AM - Engineer starts writing code... π»
-> How do ensure we didn't break all clients? <-
-> Automated testing <-
- Day 6, 11:39PM - ...Engineer uses automated testing to prove clients 1-4 behave as expected and shipsit π’
- Day 7, 8:05AM - HosOps reports good news to client π
- Day 8, 9:52AM - Client reports that it's working π
-> Things the Engineer learned <-
-> Readability <-
-> Reusability <-
-> Automated testing <-
Now imagine you are the Engineer
and sit through TODO(add stats from repos) files and functions like the ones we just wrote but more complex
and imagine those were deployed on TODO(add stats of computers) of computers in the cloud...
-> We did that this week... <-
-> Questions? <-
- Get the Presentation
- Code readability
- Code reuse
- Code refactoring
- Automated testing
- Code we wrote was in Ruby
-
Presentation specs:
- macOS Terminal with font size increased by 8
- vim via mdp
-
Unicodes from this gist
-
Use markdown to convert to HTML:
$ markdown deck.md
GistID: ad5b32e9d5e0f29cc735e2ffade15e7b