| • Coby Chapple's background and where he lives | |
| • Product design role at GitHub: focus on workflows and interactions rather than visual design | |
| • Biggest single change made to the product: enabling web-based edits to files | |
| • Importance of creating shortcuts and streamlining processes for users | |
| • Enjoyment of long-term responsibility for products and seeing how they are used over time | |
| • Blurring of lines between UI/UX: Coby focuses on what needs to happen rather than labels or silos | |
| • Code review feature | |
| • Batching code reviews into a single conversation or document | |
| • Interface problems with batching code reviews | |
| • Designing complex technical products for technical users | |
| • Balance between approachability and technical complexity | |
| • Importance of discoverability in product design | |
| • Projects feature: flexible workflows, not dictating process to users | |
| • Product expansion with the introduction of "Projects" as a new tab/page | |
| • Relationship between Issues and Projects: flexible and not strictly tied to each other | |
| • Decision to associate Projects with the repo layer of abstraction, but planning for future changes to allow for multiple repos or organization-level projects | |
| • Impact on organizational hierarchy and potential for infinite nesting | |
| • Plans for improving and expanding Projects in the future | |
| • The concept of "sherlocking" where platform providers copy features created by third-party integrators | |
| • Projects API integration and the need for basic functionality with flexibility and adaptability | |
| • GraphQL API adoption, including GitHub's decision to use it and its benefits for developers and customers | |
| • Reducing risk through dependable APIs that minimize complexity and allow for predictable development and iteration | |
| • The benefits and challenges of implementing GraphQL for API functionality | |
| • Caching and performance considerations with GraphQL | |
| • GitHub Projects' design goals and target audience | |
| • Comparison to project management tools like Trello and Pivotal Tracker | |
| • Enterprise customers' needs and the importance of customization within organizations | |
| • Wrap-up of episode | |
| • Thanks to O'Reilly for working partnership at OSCON London 2016 | |
| • Upcoming OSCON event in Austin, Texas in 2017 | |
| • Discount code for registration: "changelog20" |