Datasets:
willtheorangeguy
/
2022-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.35k
• The benefits of Go's uniform formatting include improved readability and reduced conflicts in pull requests
• Pronunciation of GoFumpt is clarified as "Go-Fumpt"
• Discussion about the naming conventions for Go, including using "Go" instead of "Golang", and the correct pronunciation of GoFormat as "Go-Funp" or "GoFund".
• Programmer preferences for styling in Go are subjective and varied.
• GoFund standardized formatting, reducing cognitive load when reviewing code.
• Its creator, Robert Grismer, doesn't agree with all of its rules but appreciates enforcement.
• Large companies struggle to implement style guidelines due to conflicting opinions.
• Having a canonical place like GoFund helps avoid debates on minor issues.
• Injecting tools like GoFund into an existing community can be challenging.
• Design decisions made early in the development process set precedents and pay dividends.
• Tooling in Go represents priorities, such as 80% of essential software engineering practices.
• GoLint and GoVet are mentioned for discussion.
• GoLint tool catches style errors and encourages best practices
• Code comments should be included for exported functions with capital letter names
• Lint rules are not enforced by the compiler but generate useful reports
• Beth and Lint differ in their approaches, with Lint focusing on style and Beth on suspicious behavior
• False positives can occur when using these tools, but they generally produce genuine reports
• Using linters like GoLint and Beth can improve code quality and make it more familiar to follow GoFund guidelines
• The difference between linting and vetting is not strictly defined, but linters focus on style and formatting issues.
• Tooling for Go development, including vet, lint, and format checking
• IDE integration, such as in VS Code, for seamless tool usage
• Importance of live feedback from code during development
• Running tests quickly and continuously while coding
• Local tool usage vs. CI/CD pipeline tools like CircleCI or Travis
• Benefits of becoming a Square solutions partner, including access to the entire Square platform and custom solutions for sellers
• Incentives and profit sharing, including a 25% SaaS revenue share and seller referrals
• Access to alpha APIs and new products
• Product, marketing, tech, and sales support
• Opportunity to get Square certified
• Use of GoTest tool for writing test codes in Go programs
• Race detector feature in GoTest for detecting potential deadlocks
• Importance of covering concrete cases in tests for effective use of the race detector
• The benefits of using Go Run for quick results and feedback
• Complications that can arise when relying solely on Go Run
• The importance of using Go Build or install instead of Go Run
• The use of the -race flag with Go Run to detect race conditions
• The trade-off between enabling the -race flag and potential slowdown in program execution
• The mixed results experienced by the speaker with large codebases and the -race flag
• The comparison of go get vs. module tools for package installation
• Difficulty in understanding GoGet and its simplicity
• Importance of being able to see code in a browser to understand what is being pulled down
• Comparison with NPM package installation and hidden dependencies
• Discussion on the value of simplicity and clarity in software development
• Mention of Go month and potential episode idea
• Use of GoGet for initial experience and distributing tools
• Discussion on cross compilation using go build and its benefits
• Experience with cross compiling on different platforms, including Docker
• The importance of intermediate assembly in compiler design
• Cross-compilation process and its benefits (faster development)
• How compilers generate machine code based on architecture
• Build tags and conditional compilation
• Using build tags for testing and including specific files depending on the target platform
• Limitations and complexities of multiple build rules and custom build tags
• Retool as a platform for building internal tools
• Community-created tools for Go development, such as Go Imports and JSON to Go service
• The Go report card website for evaluating code quality
• Godoc and its hosted service for viewing documentation
• Dominic Honneth's GoTools repo with static check tool
• Fixing Me, a GitHub integration that creates PRs with style rule changes
• Fix Me project: a tool similar to the Go report card, tightly integrated with GitHub
• Static analysis tools in Go
• Generating implementations of interfaces using a custom tool
• Performance tools in Go, including PPROF and benchmarking support
• Dynamic tools in Go for debugging and performance monitoring
• Benchmarking as a first-class citizen in certain languages creates a culture where benchmarking is prioritized.
• Effective benchmarking requires understanding of tooling and proper usage to avoid incorrect results.
• Benchmarks can be used for comparing performance of algorithms or HTTP requests, but may not provide meaningful information for complex tasks like HTTP.
• Premature optimization should be avoided, and instead, problems should be solved first, then optimized.
• Continuous profiling in production environments provides valuable data on hot calls and critical paths to inform optimization decisions.
• Optimization during development time can create fabricated problems and a culture of over-optimization.
• Profiling techniques for low overhead and continuous profiling in production environments
• Strategies for minimizing impact on critical paths, such as enabling profiling on one replica of a web server or limiting duration
• Importance of identifying hot paths and optimizing based on usage patterns
• Use of P-Prof tools for dynamic profiling and aggregation of data
• Potential for community-built tooling to support continuous integration and profiling
• Benefits of systematic optimization, including cost savings and improved performance
• GoLint became easier to satisfy
• The host made a contribution that allowed this
• The show ended with thanks and promotional announcements
• Upcoming episode featuring Ronna Steinberg discussing object-oriented programming in Go
• Partners acknowledged, including Fastly and BMC
• Call for audience engagement and recommendations
[0.00 --> 11.56] Ah, the dog days of summer. Everyone's taking time off, chilling out, maxing, relaxing all cool, maybe shooting some b-ball outside of their school.
[12.14 --> 17.64] So today we are rebroadcasting a classic episode of Go Time all about tooling.
[18.20 --> 24.26] We took you to the future a few episodes ago. Now we're headed back in time to 2019.
[24.26 --> 30.34] This was originally episode 90 and it aired almost three years ago to the day.
[30.84 --> 35.48] It was a simpler time then. Generics hadn't landed. COVID, nope.
[36.00 --> 40.12] Social distancing was only something nerds knew about. This is the way.
[40.50 --> 44.86] We didn't even have an unpopular opinions segment back then.
[45.28 --> 50.14] So some of this conversation will be quaint considering all that's changed in the world since then.
[50.14 --> 54.22] But most of it is still highly relevant. We think you'll enjoy it.
[54.44 --> 61.64] And we'll be back with some freshens next week when Natalie and Ian welcome Ronna Steinberg to discuss OOP and Go.
[66.72 --> 70.40] This episode is brought to you by our friends at Sourcegraph.
[70.48 --> 73.10] They recently launched a new feature called Code Insights.
[73.38 --> 76.34] Now you can track what really matters to you and your team in your code base.
[76.34 --> 81.10] Transform your code into a querable database to create customizable visual dashboards in seconds.
[81.46 --> 84.34] Here's how engineering teams are using Code Insights.
[84.66 --> 88.56] They can track migrations, adoption, and deprecation across the code base.
[88.80 --> 92.02] They can detect and track versions of languages or packages.
[92.46 --> 95.34] They can ensure the removal of security vulnerabilities like Log4j.