| • Steve Francia's role as Go team technical program manager with an emphasis on external usage
|
| • Community management and product management responsibilities within his role
|
| • Dependency management issues in the Go community and efforts to address them through a working group
|
| • Collaboration between the community and Google team to improve tooling awareness of dependency management
|
| • Recent survey published on the Go blog from 2016 and its findings
|
| • Francesc Campoy's role as advocate for all of Go and Google Cloud
|
| • Peter Bourgon's leadership of the dependency management working group and Sam Boyer's implementation efforts
|
| • Creation and results of the Go survey
|
| • Insights gained from the survey on user needs and challenges
|
| • Importance of establishing a baseline to measure progress over time
|
| • Growth and adoption of Go in the industry, with many users now using it at work
|
| • Difficulty finding experienced Go developers due to its relatively young age
|
| • Role of community in attracting new users and solving supply vs demand problem
|
| • Analysis of survey results on community challenges, including dependency management
|
| • Need for better resources and support for new users to adopt Go effectively
|
| • Surprise finding from survey: many people consider Go their language of most experience
|
| • Go is being used as a first language for many developers, rather than just as a conversion point from other languages
|
| • Dynamic languages (e.g. JavaScript, Python) are common backgrounds for Go users
|
| • Web development is the largest use case for Go, but also has a steep learning curve and limited documentation
|
| • Package management and lack of generics are major challenges for the language
|
| • Steep learning curve and inadequate documentation are individual challenges faced by developers using Go
|
| • The Go community lacks a centralized location for case studies
|
| • Case studies would help demonstrate the benefits of using Go
|
| • The Go team is shifting focus from early adopters to mainstream users and decision-makers
|
| • Convincing people to use Go is challenging due to its unique characteristics
|
| • Reducing the learning curve and demonstrating value are key to adoption
|
| • Improving user experience, community engagement, and contribution processes for Go is a priority
|
| • Intimidation of contributing to the Go project due to feeling like one's contributions aren't needed or that they're not smart enough
|
| • Feedback as a learning opportunity, rather than personal attack or rejection
|
| • The importance of taking feedback constructively and being willing to make changes
|
| • A culture shift from focusing on speed over perfection to striving for quality and accuracy
|
| • Different entry points into the project for those with varying levels of technical experience
|
| • Appreciation for the Go team's approach, which prioritizes getting things right rather than rushing to completion
|
| • The importance of tone in feedback and communication
|
| • Challenges faced by new contributors when receiving direct and technical feedback from the Go team
|
| • The need for encouragement and constructive feedback to help people feel valued and supported
|
| • The Go team's efforts to improve their communication style and provide a clear path forward for contributors
|
| • Examples of projects and maintainers being recognized and appreciated, such as Fatih's Vim-go project and Mark Bates' work on Go Buffalo.
|
| • Discussion of Postgres and its consistency across command line tools
|
| • Future plans for supporting other databases (Cassandra, CockroachDB)
|
| • Preference for consistent database tools to reduce learning curve
|
| • Conclusion and thank yous from the host and guests |
