Hard & Soft Skills to Avoid Outages by Pascal-Louis Perez
•
0 likes•1,217 views
In just a few years, Square has achieved ubiquitous recognition for mobile card processing grossing over $15B a year in credit card transactions. At the heart of Square's technology are many financial systems which must operate safely, correctly, and sustain rapid growth. This presentation will cover non-controversial topics such ad TDD, but from new angles. It'll also cover emerging practices like continuous deployment, and softer areas such as engineering management practices geared towards safety. You'll come out of this session with a fresh perspective on how to build software.
Recommended
More Related Content
Similar to Hard & Soft Skills to Avoid Outages by Pascal-Louis Perez
Similar to Hard & Soft Skills to Avoid Outages by Pascal-Louis Perez (20)
More from Hakka Labs
More from Hakka Labs (20)
Recently uploaded
Recently uploaded (20)
Hard & Soft Skills to Avoid Outages by Pascal-Louis Perez
- 1. Hard & Soft Skills to Avoid Outages @pascallouis from @SquareNY
- 5. Tactics • Fighting mixing ids • Entity bound ids (e.g. Id<T>) • Textual ids MWDN-YP89-OLVL-USER • Testable configurations • etc. Code Bless Ship Maintain Profit! git rm
- 6. TDD • Not controversial (anymore) • Living code documentation • Enables collaboration • Technique to encode invariants Code Bless Ship Maintain Profit! git rm
- 7. Gold Tests • Tests which can be changed by a (small) subset of engineering • Enforced via policy or technology Code Bless Ship Maintain Profit! git rm
- 8. Expressive Tests • “Change your language and you change your thoughts” — Karl Albrecht • Can be implementation agnostic Code Bless Ship Maintain Profit! git rm
- 9. ... Given feed PaymentEventFeedListener receives: """ { "payment_id": "EPT-300", "isTivoReplay": false, "merchant": { "token": "m-1" }, ... } """ Then expect table balance_changing_events order by id: | event_type | status | process_attempts | | HOLD | UNPROCESSED | 1 | | CAPTURE | UNPROCESSED | 0 | When then the time is 2012-01-06 17:10:00 And balance changing event queue processes items Then expect table balance_changing_events order by id: | event_type | status | process_attempts | | HOLD | UNPROCESSED | 2 | | CAPTURE | PROCESSED | 1 | Code Bless Ship Maintain Profit! git rm
- 11. Code Analysis • In theory: static vs dynamic • In practice: pre vs post-production Code Bless Ship Maintain Profit! git rm
- 12. Pre Analysis • Type Checking • Testing, CI • Linters • Forbidden Call Analysis Code Bless Ship Maintain Profit! git rm
- 13. Post Analysis • Logging • Metrics • Invariant Checking Code Bless Ship Maintain Profit! git rm
- 14. Speaking of Alerts: Metrics vs Checks OK ? WARNING 1 0 200ms 0ms Code Bless Ship Maintain Profit! git rm
- 16. Fix It Weeks • Time set aside, monthly or quarterly • No top-down mandate except “fix it” Code Bless Ship Maintain Profit! git rm
- 18. Post-Mortem • When Anytime there are issues! • Why Learn and avoid mistakes of the past • How Blameless Code Bless Ship Maintain Profit! git rm
- 19. Post-Mortem • Go through the timeline • The Good, The Bad and the Ugly • Action Items Code Bless Ship Maintain Profit! git rm
- 22. Proportional Investing • When you lose N hours to maintenance, you spend an equivalent N hours on improving things. Code Bless Ship Maintain Profit! git rm
- 23. Safety drives productivity; and unleashes creativity. Technology, sure. But, it’s mostly about culture and people. Many layers of defense, lots of ways to do it — find what’s right for your team.