text stringlengths 0 2.35k |
|---|
But yeah, beyond those use cases - man, solve the problem first, and then worry about organizing it, then worry about abstractions, then worry about what's being used and reused and things, and don't be shy to copy from across projects even. Just don't be afraid; you can just copy a file here and drop it in your projec... |
**Kris Brandow:** So if you were to write a blog post on how you should organize your Go code, it would just say, "Don't." |
**Johnny Boursiquot:** Don't. \[laughs\] |
**Kris Brandow:** Like, by the time you need to organize your codebase, you won't need a blog post to tell you how to do it. |
**Johnny Boursiquot:** Exactly. |
**Kris Brandow:** We just publish that on the Changelog blog right now... \[laughter\] No, I mean, I definitely agree with that. I think people do rush way too fast to try and sit down and organize their codebases. I personally always start with one file, one package, just put everything in it, and then once it starts ... |
**Johnny Boursiquot:** Whoa, whoa, whoa! This is where you and I fork. \[laughs\] A thousand lines long file? No, you and I are going to have words... \[laughter\] |
**Kris Brandow:** \[56:08\] Disagreements! We'll have a whole episode about this. Whether it stays at 1,000 lines is debatable, but I think files are -- I'm more okay with people splitting things up into files. I think the thing I like to avoid is people that make 40 files with 20 lines of code in them. There's a middl... |
**Ian Lopshire:** I think I did. This might be a repeat, though. I don't know. |
**Kris Brandow:** Okay. |
**Ian Lopshire:** My unpopular opinion right now is that monoliths are probably the way to go for most companies right now. I think all these companies going microservices are doing one of those things where "Microservices are best practice, so we're just going to mindlessly do it", and not thinking "Why am I doing thi... |
**Johnny Boursiquot:** Wait, we haven't learned from all the case studies of people who went micro and went back to, I guess, macro, or monolith, or something? A lot of times people think that, "Yeah, I'm going to adopt microservices, because it's cool and trendy and whatnot." And they're realizing that when you go mic... |
So your developers, while they may have input into the decision to microservice or not to microservice, I think the operational folks, the SREs, the people who need to keep this thing running and orchestrate all the things and deploy all these things across infrastructure, make your thing into a distributed system that... |
**Kris Brandow:** See, we've just got to rebrand monoliths into macroservices, and that will be the new hotness, and that's how we can get people over macro. It's like, "Obviously, macroservices are better, because they're bigger, right? Macro. Why would you do something micro when you can do a macro? It's innovation. ... |
Alright... So yeah, we'll put the polls up on Twitter and see if your unpopular opinions are actually unpopular. I am curious to see if they are. And as the rule goes, if they're not, you have to come back and try again, to be unpopular. |
**Johnny Boursiquot:** Justify. |
**Kris Brandow:** And perhaps one day you will be as unpopular as some of my opinions have been, to once again, warrant us some negative reviews on Apple Podcasts. If you liked the podcast, go and give us a nice review on Apple Podcasts, please. But yeah, with that, I want to thank you, Ian, for joining us for this lov... |
**Ian Lopshire:** Yeah. Thanks for having me. |
**Kris Brandow:** Yeah, of course. And thank you, Johnny, for co-hosting, as always. Hopefully, we didn't get too meta for our listeners out there. |
**Johnny Boursiquot:** Just the right amount. |
**Kris Brandow:** Just the right amount. |
• Definition of a beginner in programming |
• Types of beginners: those who know one language but want to learn another, career-transitioning individuals with no prior programming knowledge, and curious kids who like to break technology |
• Importance of clear explanations and foundation for absolute beginners |
• A Gentle Introduction to Golang for Beginners course by Dave Valentine on Udemy |
• The need to trust the content creator and structure when learning new concepts |
• The value of self-paced learning and coming back to more complex topics later |
• Discussion of industry trends and shift towards self-taught developers |
• Comparison between university CS degrees and alternative paths (bootcamps, online courses) |
• Personal journeys and experiences with learning programming languages (Go, Python) |
• Strategies for teaching and learning Go, including creating a "roadmap" and providing resources for continued learning |
• The importance of hands-on experience and building projects in learning to code (Gophercises) |
• Debating the effectiveness of advice to "just build something" vs. having a clear plan and doing it multiple times |
• Building something multiple times to solidify understanding |
• Importance of repetition in learning |
• Unique challenges of learning Go, including GOPATH setup |
• Simplifying setup and entry points for new learners |
• The role of environment variables and platform-specific issues in setup |
• The need for simple, straightforward setup processes for beginners |
• Setup difficulties in Go as a barrier to entry |
• The need for beginner-friendly content and materials |
• Comparison of setup experiences between different programming languages |
• The importance of visual aids and interactive tools for learning Go |
• Potential for an ELI5 (Explain It Like I'm 5) segment on the Go Time podcast |
• Discussion of creating children's books or educational resources for beginners |
• Collaborative efforts to create more beginner-friendly content and materials |
• Pros and cons of learning mediums: video courses, workshops, written tutorials |
• Accessibility issues with automated closed captioning in videos |
• Difficulty in iterating and making changes in online video platforms |
• Importance of collaboration and feedback loops in online learning environments |
• Scaling traditional teaching methods to accommodate rural and suburban learners |
• Online mentorship programs as a way to facilitate community-driven learning |
• Gophercises content and support |
• Go 101/201 foundation and next steps |
• Resources for learning Go (Awesome Go, libhunt.com) |
• Importance of community and inclusive coding environments |
• Open source projects as a way to learn and contribute |
• GitHub features for onboarding new contributors (Great first issue, FirstTimersOnly) |
• The importance of asking questions in programming and creating a safe environment for beginners |
• The difference between learning a new language on the job versus on one's own time |
• How to create an interactive and non-intimidating atmosphere for learning and question-asking |
• The impact of answer style on encouraging or discouraging further questions and exploration |
• Potential gaps in existing content resources for programming and learning |
• Discussing the "letter to your past self" survey question |
• Common headaches in learning a new programming language (Go) |
• Tips for improving coding skills and overcoming obstacles |
• Importance of community engagement and resources (GopherSlack, meetups) |
**Carmen Andoh:** Welcome back, everyone, to Go Time. I am Carmen Andoh and Mat is out this week, so I will be your host for the journey. Joining me today is our recurring panelist, Ashley McNamara. Say hello, Ashley. |
**Ashley Willis:** Hello, everyone. |
**Carmen Andoh:** And we have a returning guest, Jon Calhoun, who is the content founder for Gophercises.com, but also UseGolang.com, TestWithGo.com, ErrorsInGo.com... So I'm excited to have you on, Jon. Say hi. |
**Jon Calhoun:** Hey, everybody. |
**Carmen Andoh:** And now we have a new guest, Dave Valentine. He's the instructor of Udemy's A Gentle Introduction to Golang for Beginners. Welcome to our show! |
**David Valentine:** Thank you so much! It's a pleasure to be here for the first time. |
**Carmen Andoh:** Speaking of beginnings, when we asked Dave to show up on the show and give a profile pic, he submitted one of him as like a toddler, with TRS-80 Model 1, circa 1980... I think that's probably when you began? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.