35
Developing at scale What’s it like at Capital One?

Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

  • Upload
    others

  • View
    2

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Developing at scaleWhat’s it like at Capital One?

Page 2: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

First, let’s take a look at what you’ve used so far...

Page 3: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 4: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Your Audience = Classroom (~20 people)

+ your professor+ your friends

Feedback

Page 5: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Experience of Rachel, our intern

Coming from University to Capital One for 10 weeks

Page 6: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Team Structure

Page 7: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Agile Delivery Lead

Product Owner Tech Lead Business Analyst

Mobile Dev Mobile Dev Mobile Dev

Page 8: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Onboarding Documents

Page 9: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Learning the app + the audience

Page 10: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Audience

Page 11: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Release Cycle

Page 12: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

2 weeks 1 week

Daily Stand Up

Grooming new features

Regression Testing

Retrospective

Next Sprint’s Planning

Page 13: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Tools + Process

Page 14: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 15: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Architecture

Page 16: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 17: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Learning the Architecture

MVVM

or MVP.. or MVI.. or MVC.. or MVWTF...

Page 18: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Organizing re-usable components and modules

Across teams

Managing repositoriesManaging versionsManaging publishing/upgradesManaging dependenciesManaging timelines

Page 19: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Podfile example

Page 20: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Testing

Page 21: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 22: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 23: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 24: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 25: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 26: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 27: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 28: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 29: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 30: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 31: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 32: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 33: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Feedback + Data + Analysis

Page 34: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)
Page 35: Developing at scaleDI helps make code more testable Most apps interact with system or library objects — objects you don't control — and ... Data Binding UI Logic (Code Behind)

Repeat for next cycle