We often have code that’s similar between projects and we find ourselves copying that code around. In this episode we discuss what to do with this common code, how to organize it, and what code qualifies as this common code. Join the discussionChangelog++ members save 5 minutes on this episode because they made the ads disappear. Join today!Sponsors:Square – Develop on the platform that sellers trust. There is a massive opportunity for developers to support Square sellers by building apps for today’s business needs. Learn more at changelog.com/square to dive into the docs, APIs, SDKs and to create your Square Developer account — tell them Changelog sent you. Sourcegraph – Move fast, even in big codebases. Sourcegraph is universal code search for every developer and team. Easily search across all the code that matters to you and your organization: find example code, explore and read code, debug issues, and more. Head to info.sourcegraph.com/changelog and click the button “Try Sourcegraph now” to get started. FireHydrant – The reliability platform for every developer. Incidents impact everyone, not just SREs. FireHydrant gives teams the tools to maintain service catalogs, respond to incidents, communicate through status pages, and learn with retrospectives. Try FireHydrant free for 14 days at firehydrant.io SignalWire – Build what’s next in communications with video, voice, and messaging APIs powered by elastic cloud infrastructure. Try it today at signalwire.com/video and mention “Go Time” to receive an extra 5,000 video minutes. Featuring:Ian Lopshire – Twitter, GitHubKris Brandow – Twitter, GitHubJohnny Boursiquot – Twitter, GitHub, WebsiteShow Notes: Thoughts on how to structure Go code Something missing or broken? PRs welcome!

New Go developer questions answered - best practices, language quirks, reimagining alerting with FireHydrant, error handling tips, project management, database handling, concurrency with mutex and channels

This week we’re sharing the most popular episode of Go Time from last year — Go Time #196. We believe this episode was the most popular because it’s all about building actually maintainable software and what goes into that. Kris Brandow is joined by Johnny Boursiquot, Ian Lopshire, and Sam Boyer. There’s lots of hot takes, disagreements, and unpopular opinions. This is part two of a three part mini-series led by Kris on maintenance. Make sure you check out Go Time #195 and Go Time #202 to continue the series. Join the discussionChangelog++ members save 6 minutes on this episode because they made the ads disappear. Join today!Sponsors:InfluxData – All of the open source software InfluxData creates is either MIT-licensed or Apache2-licensed. These are very permissive licenses. But why are they all for permissive licenses? Paul Dix shares his thoughts on the spirit of open source and why freedom, evolution, and impact drive them to license InfluxData’s open source software as permissively possible. Learn more at influxdata.com/changelog Square – Develop on the platform that sellers trust. There is a massive opportunity for developers to support Square sellers by building apps for today’s business needs. Learn more at changelog.com/square to dive into the docs, APIs, SDKs and to create your Square Developer account — tell them Changelog sent you. Honeycomb – Guess less, know more. When production is running slow, it’s hard to know where problems originate: is it your application code, users, or the underlying systems? With Honeycomb you get a fast, unified, and clear understanding of the one thing driving your business: production. Join the swarm and try Honeycomb free today at honeycomb.io/changelog Retool – The low-code platform for developers to build internal tools — Some of the best teams out there trust Retool…Brex, Coinbase, Plaid, Doordash, LegalGenius, Amazon, Allbirds, Peloton, and so many more – the developers at these teams trust Retool as the platform to build their internal tools. Try it free at retool.com/changelog Featuring:sam boyer – Twitter, GitHubIan Lopshire – Twitter, GitHubKris Brandow – Twitter, GitHubJohnny Boursiquot – Twitter, GitHub, WebsiteShow Notes: Go Time #195 Go Time #202 Uber’s Go Style Guide Why smart engineers write bad code Rant about “performant” Something missing or broken? PRs welcome!

Discussing the challenges of diving into unfamiliar codebases, exploring the importance of knowledgeable guides, good documentation, and experienced team members. Delving into tracing functions in different languages, using interfaces, and navigating codebase changes. Touching on the significance of meaningful data collection, observability, and effective knowledge management. Advocating for discipline, clarity, and gradual improvements over rash rewrites.

Johnny Boursiquot, known for his engaging workshops, joins the conversation to discuss the most intriguing tech opinions of 2023. They dive into the benefits of starting with a monolithic architecture before moving to microservices, sharing humorous anecdotes along the way. The group reflects on unconventional perspectives regarding web browsers and programming languages, critiquing Python's evolution. The episode wraps up with a light-hearted debate about tech, cooking, and IntelliJ IDEs, all sprinkled with clever insights.