text stringlengths 0 2.35k |
|---|
And then with a lot of biotech software, they're like "Just believe me that it's good. Please, give me $100,000 to start, before we even show you the code. Just believe me." And so it's a big difference there. And then you get into -- you know, there's obvious code quality, then you have people that are submitting pull... |
So there is some real value to it, especially if you're not the traditional purveyor of truth, if you're not the PhD who's gone to Harvard, who's the fancy guys, fancy guys, grad students... It's a great way to show that you're the best, and you've got the right stuff. |
So I feel like there's gonna be more companies, hopefully, like GitLab, Red Hat, MongoDB... And I'm hoping companies like Gitpod, and NextFlow, sort of get to this IPO stage too, where people can see the engineer, and they can see the service, they can see the value in it, and they don't care that it's open source, bec... |
**Natalie Pistunovich:** I agree with you very much. |
**Tim Stiles:** Really? Okay. So it's not controversial, and I've ruined the segment. |
**Ian Lopshire:** I think it might be controversial... |
**Natalie Pistunovich:** Yeah. So there will be a vote... As with every unpopular opinion, we will put this on our Twitter and we'll see how many people agree or disagree with you. But to summarize it, we said that your unpopular opinion is that open source always has been sustainable, and... Yeah, we'll see how that g... |
**Tim Stiles:** Oh God, I'm so sorry... \[laughter\] |
**Natalie Pistunovich:** No, that's amazing. You taught us so much, and I want to say thank you very much for that. |
**Tim Stiles:** I wish I had a whiteboard. I'm gonna have to go and make a new PowerPoint presentation... |
**Natalie Pistunovich:** I learned one million things today. |
**Tim Stiles:** Okay. Alright. If anyone is out there listening to this, or you, Natalie, or Ian wanna ask more questions about biology, I'm always available. I may get tired of it eventually... |
**Natalie Pistunovich:** And your Twitter is mentioned here, for sure. |
**Tim Stiles:** Oh, yeah. This is the Twitter. If you jump in the Discord, there's gonna be hopefully some nerd that'll be like "I know that bit of biology." I love my Discord for that. Someone can be like "Yeah, I can explain that." I'm like, "Great. I had no idea." |
**Natalie Pistunovich:** Perfect. We'll add the Discord to the show notes as well. And Ian, thank you so much for joining, and co-learning here, live. Tim, thank you for teaching us so many things. This was really fascinating. |
**Ian Lopshire:** It was. |
**Tim Stiles:** Thank you for having me. I hope I did alright... |
**Natalie Pistunovich:** It was amazing. |
**Ian Lopshire:** Amazing, yeah. |
**Tim Stiles:** Alright. |
**Natalie Pistunovich:** Thanks, everyone who joined. |
**Tim Stiles:** Thank you very much. Talk to you later. Bye! |
• Introduction to Go Time episode on tooling |
• Jaana Dogan's return to the show after traveling for work and her upcoming new role at an undisclosed company |
• Johnny Boursiquot's recent start in a new job and his experiences with the "honeymoon period" |
• Discussion of the benefits and features of `go fmt` (the Go format tool) |
• Etymology and pronunciation of `fmt` and "golang" |
• Consistency in coding style with go fmt |
• Importance of creating community culture around tooling from the start |
• Benefits of early decisions on testing and prioritizing essential software engineering practices |
• Differences between Golint (style errors) and Govet (lint is more about suspicious patterns) |
• Value of using linter and vet tools together as part of a toolchain, including plugins and extensions in editors like VS Code and Vim. |
• Benefits of using tools such as go fmt, go vet, and gometalinter (now called golangci-lint) for code quality and debugging |
• Importance of running tests quickly and frequently, especially with unit tests |
• Value of live feedback from the code during development, including linter messages and test results |
• Advantages of using continuous integration (CI) tools to run these checks on remote servers and ensure code quality |
• Fast and useful Go tools, such as go fmt, go vet, and gometalinter, that integrate well with IDEs |
• Use of the race detector in go test to catch potential deadlocks and concurrency issues |
• Importance of writing tests that cover concrete cases for the race detector to be effective |
• Go build and run commands |
• Race detector option with -race flag |
• Comparison between make command and go build/run |
• Go get tool for installing packages |
• Module tools vs. GOPATH world |
• Cross-compilation using GOOS and GOARCH flags |
• Benefits of simplicity and transparency in package management |
• Cross-compilation in Go and how it works |
• Build tags for conditional compilation |
• Intermediate assembly language used by compilers |
• goimports tool for formatting code and resolving imports |
• JSON-to-GO service for generating Go structures from JSON |
• Go Report Card website for evaluating code quality |
• GoDoc for viewing documentation and static analysis tools like Staticcheck |
• Generating implementations of interfaces using a tool that takes the interface and creates a concrete implementation |
• Using AST (Abstract Syntax Tree) tools from the standard library for code generation |
• Performance tools and benchmarking support in Go, including pprof and go test |
• Importance of benchmarking in understanding performance and making informed optimization decisions |
• Risks of premature optimization and focusing on solving problems first before optimizing code |
• Continuous profiling in production to identify hot paths and optimize performance |
• Using pprof tools for low-overhead profiling without impacting critical paths |
• Importance of identifying hot paths before optimizing code |
• Difficulty with continuous profiling due to lack of built-in features in Go |
• Idea of creating a tool or library for automatic continuous profiling reporting |
**Mat Ryer:** Hello, and welcome to Go Time. I'm Mat Ryer, and on today's episode we're talking about tooling. All those great tools that help us be successful, help us do our job. We use the Go tools all the time, every day. We use them for building, for running code, for testing, we use them for formatting our code, ... |
I think this show will be useful to anybody new to Go that wants to get a sense of the tooling that we all use. I'm sure there will also be some golden nuggets for the seasoned gophers also... And I'm so confident because of who's joining me. I'm joined today by - in no particular order - Jaana Dogan. Hello, Jaana. |
**Jaana Dogan:** Hello, hey! |
**Mat Ryer:** Welcome back to Go Time! How have you been? |
**Jaana Dogan:** Yeah, it's been a while. I've been traveling, I guess. |
**Mat Ryer:** Yeah, yeah. Where did you go? |
**Jaana Dogan:** I was in Marbella, Spain. The last time we talked I was just going for a conference, and then I never came back to the show. I'm so sorry... |
**Mat Ryer:** That's alright. I can understand. This year you're off on travels to exotic places for work... It's a tough life. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.