How much do you know about a career in coding? Perhaps you're already a well versed professional software person. Or maybe you're someone who's just starting out. Either way, you're going to need some help along your entire technology career. In this episode, which is part 2 of a 2 part series, the panel is chatting with Chris Allaire to talk about all things tech recruiting! They discuss what makes one a good candidate, why a recruiter is useful, whether recruiting can be replaced with AI, and so much more. As always, we've got some great unpopular opinions at the end.Thanks for tuning in and happy listening!Notes & Links:AverityChapters:(00:00) - Intro
(00:57) - How're we doing?
(01:47) - Introducing Chris Allaire
(03:30) - Retro Tech Recruiting
(08:44) - Recruiting Throughout The Decades
(13:17) - Increasing Specialization. Or Not.
(17:02) - Modern Tech Recruiting
(27:47) - Fearing Automation
(35:45) - What makes a good candidate?
(42:33) - Senior vs Staff: Knowing The Job You want
(47:23) - Starting A Career In Coding
(55:51) - For Those Who Love Tech, But Not Coding
(01:00:57) - How To Choose The Right Company
(01:13:03) - Unpopular Opinions
(01:13:48) - Chris' Unpop
(01:16:10) - Dylan's Unpop
(01:17:43) - Kris' Unpop
(01:20:18) - Ian's Unpop
(01:22:50) - Final Advice: Get A Recruiter (who cares about you)!
(01:25:23) - Outro
Hosts
Kris Brandow - Host
Ian Wester-Lopshire - Host
Dylan Bourque - Host
Chris Allaire - Guest
Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram
--------
1:25:55
An Exploration of Complexity
Modern software development feels so complex. In this episode, Ian Wester-Lopshire is joined by Kris Brandow, Matthew Sanabria, and Angelica Hill to discuss complexity. They propose hypotheses for the root cause of complexity, explore the ways complexity affects our technology and organizations, and ponder if artificial intelligence can aid us in reducing complexity. As always, we've got some great unpopular opinions at the end.As always thanks for tuning in and happy listening!This episode is a pilot for a planned mini-series on complexity. We'd like to explore complexity deeper by having conversations with and interviewing a diverse set of people. Do you have thoughts about complexity, know someone who thinks deeply about this topic, or have something you'd like to add? Reach out to us on social media and let us know!Notes & Links:CPU.fmChangelog & Friends #77Chapters:(00:00) - Intro
(00:31) - How are we doing?
(01:24) - Where did complexity come from?
(02:53) - Ian's Hypothesis
(07:00) - Kris' (Hot Take) Hypothesis
(14:38) - FAANG & Engineering Excellence
(19:21) - Do better practices lead to complexity?
(24:02) - The Cloud's enablement of complexity
(24:39) - Some of the complexity is worth it
(26:01) - Systems become more complex over time
(27:33) - Moving Faster & Thinking Less
(31:18) - Accidental complexity
(31:47) - Where else does complexity surface?
(32:03) - Human Organizations & Trading Complexities
(37:46) - Documenting Decisions
(38:20) - Hypoethsis: Bad information organization is the root of complexity
(49:01) - Can AI be our librarian?
(54:39) - Search is not a text box
(55:57) - Machine learning for indexing
(01:00:17) - Can AI write our code?
(01:05:44) - Easy & Hard Learning
(01:12:27) - Hypothesis: mixed and unclear terminology
(01:14:46) - Concise Hyopthesis of Complexity
(01:18:05) - Letters by mail?!
(01:18:56) - Unpopular Opinions
(01:19:14) - Matthew's Unpop
(01:23:10) - Ian's Unpop
(01:28:30) - Kris' Unpop
(01:35:47) - Fallthrough & CPU.fm
(01:37:39) - Complexity Mini-Series
(01:38:26) - Outro
Hosts
Kris Brandow - Host
Ian Wester-Lopshire - Host
Matthew Sanabria - Host
Angelica Hill - Producer
Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram
--------
1:39:31
Do We Think You Should Learn To Code?
For years we've been told that everyone needs to learn to code. As career software people, what are our thoughts on this? Should you learn to code? Is coding the right career for you? In this first episode of a two part series, the panel discusses how they learned to code, whether they think everyone should learn to code, and of course they offer up some unpopular opinions.And if you're thinking, "I already know how to code", don't worry, this episode contains valuable advice for you as well.As always thanks for tuning in and happy listening!Notes & Links:Ben Eater's YouTube Channel (from 53:00)John Carmack's Fast Inverse Square Root (from 1:01:47)This is actually from Quake, not Doom.Change Interviews #581 It's Not Always DNS (from 1:04:15)Chapters:(00:00) - Intro
(01:33) - How're we doing?
(04:41) - Why did we learn to code?
(06:10) - Why Kris learned to code
(07:44) - Why Ian learned to code
(08:54) - Why Dylan learned to code
(10:36) - Why Matthew learned to code
(14:22) - Computer Assembly Not Required
(16:51) - Tangent: Why Are USB-C Cables?
(17:36) - Should you focus on a specific language?
(22:45) - Do you want to solve problems?
(24:53) - Coding & Woodworking
(27:09) - Curiosity & Itches that need scratching
(31:07) - What do we mean when we say "code"?
(32:34) - You should learn Excel
(39:35) - Coding Is Configuring Computers
(43:32) - Discrete Math, Not Binary
(47:03) - Learn the low level stuff... eventually
(53:42) - The desire to learn
(57:41) - Sidequest: Networking
(01:05:52) - Learning Design & Being Load Bearing
(01:12:10) - Continual Learning
(01:14:33) - What of AI and Automation?
(01:21:49) - Share What You Learn
(01:24:24) - Should You Learn To Code?
(01:24:57) - Teaser: Episode 5 - Is Coding The Career For You?
(01:26:02) - Unpopular Opinions
(01:26:08) - Matthew's Unpop
(01:28:51) - Ian's Unpop
(01:29:29) - Dylan's Unpop
(01:33:52) - Kris' Unpop
(01:36:50) - Tangent: Chopper?
(01:37:27) - Outro
Hosts
Kris Brandow - Host
Ian Wester-Lopshire - Host
Dylan Bourque - Host
Matthew Sanabria - Host
Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram
--------
1:38:38
The Gems & Warts of Go
Gems are the things we love, and warts are the things we don't. On today's episode, Kris is joined by the hosting panel of Ian, Matt, and Dylan and they are talking about the gems and warts of Go. From defer, to net/http, to vanity URLs, to modules, we cover around 30 topics! To prevent our listeners/viewers from returning an E_TOO_MANY_UNPOPS error, we didn't include the Unpopular Opinions segment (there are plenty throughout the episode). We hope you enjoy this tangent filled episode. Have a gem or wart you agree/disagree with or think we missed a few? Let us know on social media or in the comments!Thank you so much for listening. Happy listening!Notes & Links:Chandler Carruth's CPPcon talk (from 40:44)Go x/tools/guru (from 43:36)Since deprecated, however this functionality is included in gopls.go/analysis (from 47:19)go/x/tools/cmd/eg (from 1:47:25)go/x/tools/refactor/egeg documentationChapters:(00:00) - Intro
(00:31) - Introductions
(05:07) - Gem#1: net/http
(07:37) - Gem#2: defer (gem)
(09:36) - PEBKAC (tangent)
(11:36) - Gem#3: if err != nil (gem)
(16:09) - Gem#4: testing included (gem)
(19:13) - Gem#5: struct field tags (gem)
(21:57) - Gem#6: reflect & unsafe (gem)
(24:35) - Gem#7: sync/atomic (gem)
(24:54) - Gem#8: io as composeable interfaces (gem)
(25:32) - Gem#9: No inheritance (gem)
(31:20) - Gem#10: Vanity URLs (gem)
(34:33) - Gem#11: single for loop (gem)
(37:08) - Gem#12: pprof (gem)
(38:25) - Gem#13: security by default (gem)
(40:01) - Gem#14: fast compiler times (gem)
(41:16) - Gem#15: go/ast & go/* packages (gem)
(42:05) - Gem#16: implicit interfaces (gem)
(42:38) - Wart#1: implicit interfaces (wart)
(48:37) - Wart#2: slice tricks (wart)
(54:10) - Wart#3: lack of method overloads (wart)
(56:57) - Wart#4: covariance for array parameters (wart)
(59:38) - Wart#5: encoding/json marshalling unexported fields (wart)
(01:01:27) - Wart#6: encoding/json marshalling errors (wart)
(01:02:31) - Wart#7: single letter variable names (wart)
(01:08:45) - Wart#8: iota (wart)
(01:16:09) - Wart#9: map operations (wart)
(01:18:23) - Gem#17: structs as map keys (gem)
(01:20:04) - Wart#10: main function signature (wart)
(01:23:35) - Gem/Wart#1: channels (gem & wart)
(01:30:38) - Wart#11: range loop variables (wart)
(01:34:31) - Wart#12: no standard build system (wart)
(01:38:09) - Wart#13: modules (wart)
(01:53:18) - Outro
Hosts
Kris Brandow - Host
Ian Wester-Lopshire - Host
Dylan Bourque - Host
Matthew Sanabria - Host
Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram
--------
1:57:15
War Stories
Our experiences are what make us the software people we are today. In this episode, Kris is joined by the hosting panel of Ian, Matt, and Dylan and they're talking war stories. You'll hear tales of coworker frustrations, our own hubris, and plenty of weird software bugs. To close the episode out, Dylan, Ian, and Kris provide some unpopular opinions! Let us know on social media if you think their opinions are unpopular as they seem to think they are!Thank you so much for listening to our first episode. Happy listening!(00:00) - Introduction
(00:43) - Talkin' Bout The Rain
(01:39) - Dates, Times, and "Helpful" Platforms
(14:17) - Y2K Flashback
(16:20) - Non-Refreshing Refresh Tokens
(21:53) - TCP, Locks, and Load Balancers
(34:16) - tar != tar
(39:52) - Bonus Story: Too Many Modules
(43:58) - pprof to the rescue!
(47:18) - netcat: the ultimate database backup tool
(49:03) - The Perfect API (In Theory)
(53:30) - Hubris and the ease of ETL
(55:38) - Problems with Proactive Fixes
(58:39) - Unpopular Opinions
(59:00) - Dylan's Unpop
(01:03:08) - Ian's Unpop
(01:09:26) - Kris' Unpop
(01:12:32) - Outro
Hosts
Kris Brandow - Host
Ian Wester-Lopshire - Host
Dylan Bourque - Host
Matthew Sanabria - Host
Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram
España