Hi folks,In this episode I say a tearful adieu.  I have taken a very exciting new role at Sourcegraph, and I only want to talk about that from now on, so I'm semi-retiring this podcast.I will release a few episodes a year on this channel, and I will likely put more work than usual into them, so stay subscribed if you would like to see occasional new drops on this channel.Thanks so much for listening, and I hope to see you all on my Sourcegraph talks!Cheers,Steve

Featuring special guest Alex Eagle, Founder and CEO of Aspect.dev, which specializes in Enterprise Bazel support.  I worked with Alex for years back at Google and we both have a ton of respect for the Bazel build system, which is the open-source version of Blaze (Google's internal build system).I have some sound issues on my end this week, though Alex's sound came out great.  But the biggest problem with this week's episode is that my stream (in postproduction) wound up about 1.5 seconds ahead of Alex's, so I respond (and often begin) too quickly. I tried to clean it up during editing but the damage was done. Sorry about that.Please send me ideas for stuff you want me to talk about - LinkedIn works well for me:  https://www.linkedin.com/in/steveyegge/

Hey folks!  Today's episode is an intro to Service Meshes.There are many, many players in this space, and I only talk about a few of them.  Notably I left out Buoyant, which provides a mesh based on linkerd.  So this is not a full comparison of all possible options. But it does cover a lot of the big ones.This episode has some sound and picture issues.  I recorded it in my guitar/music studio instead of my regular studio, because I am considering consolidating them and wanted to try out a temp setup.  It worked OK, but I had some serious mic issues in the middle, and lots of extraneous noise and bumps.  For which I apologize!Also, everything in this second studio is not as good -- the lights, the mic, the audio interface, the green screen, pretty much the whole setup.  So it doesn't look great. I'll keep tinkering with it. I'm sure it'll get better.Fair warning: My talk today is heavily biased towards HashiCorp products, which are generally open source, albeit with enterprise features -- a standard industry model. I also give some strong shoutouts to Kong Inc.  I am not in ANY way affiliated with HashCorp nor Kong Inc, and nobody has paid me to do this talk. This is all just my personal opinions from having worked with some of the technologies in question.In last week's episode I had the (hopefully original) insight that managers are the data plane in the company's "organizational service architecture". This episode should give you enough background that we can explore that analogy further in an upcoming episode. Should be fun!If you like this content, please go over to YouTube and Like the video, comment below; and, if you can find it in your heart, also subscribe to my channel. Each of these small actions helps *tremendously* with the YouTube algorithms that can help my channel grow. And please share this with others if you think they would find it useful.

Hey folks,Someone asked me for career advice on whether they should make the jump over onto the management track.  We had a nice conversation about it and I decided to give a little talk on it this week.I had some technical issues and wound up getting delayed a day; my apologies.I also apologize that the editing is a bit choppy. It's a little bit of a bumpy ride, but I wanted to keep myself on topic and I wound up deleting a good 25-30% of the talk.  I hope it's intelligible.If you like this content, please share it with others!

In this exciting discussion, Jeff Atwood, co-founder of Stack Overflow and creator of Discourse, shares his insights into the evolution of online programming communities. He reflects on his $10k bet with John Carmack about self-driving cars and debates their future autonomy. Jeff also dives into the transformation of hardware, recalling anecdotes from the gaming industry, and outlines the unique approaches of Stack Overflow and Discourse in fostering engagement and quality discussions. A must-listen for tech enthusiasts!

After two years of retirement, the speaker shares their decision to return to the tech industry. They discuss the evolving landscape of job searching versus their earlier experiences, highlighting today’s demand for programming skills. The challenges of wealth disparity in remote work are explored, alongside reflections on leadership dynamics in tech. As they navigate their personal journey, the speaker contemplates how technology can address societal issues while seeking to redefine their professional path in a meaningful way.

Hey folks!  This was an overly-ambitious attempt to do a mini-lecture on the Farmer, Dog, Chicken, Grain puzzle and its programming solutions.This was one of the homework questions I had in my Intro to Programming Languages course in the University of Washington's undergraduate Computer Science program, taught at the time by Linda Shapiro. She had us solve this problem in Lisp, Smalltalk, and Prolog.So this is a fairly in-depth technical discussion that might seem a BIT on the boring side, compared to some of my other episodes. But it's 100% something you could find in a computer science course.I'll find a way to. upload the code somewhere, since there's no code formatting available here.

Hey folks!This week I talk about Ruby, which is one of my Top 3 favorite programming languages (if you count "Lisp" as a single language), the third being Kotlin.If you want to get straight to the hand-waving ranting, you can jump to around the 40 minute mark.This week we're having a competition!  We're going to re-do the Farmer, Dog, Chicken, Grain competition I held at Amazon.com around 18 years ago.Sometime this week, if you have time, try writing a succinct and elegant solution to this problem, in the programming language of your choice, and post it here in the YT comment section.The problem:  A farmer (F) needs to get his dog (D), chicken (C) and bag of grain (G) across a river. He has a boat that allows him to carry exactly zero or one item across with him. Write a program that spits out a solution when you run the program with no input/arguments.Example solution that your program might output:  carry chicken  carry nothing  carry grain  carry chicken  carry dog  carry nothing  carry chickenYou can model it however you like.  Below I present an abstract model of the states of the system as it carries out the steps above, where | represents the river. Things on the left bank and right banks are placed before/after the '|', respectively:FDCG| - start state, everyone on left; carry chicken to right bankDG|FC - FC now on right; carry nothing backFDG|C - FDG on left; carry grainD|FCG - FCG on right; carry chicken backFCD|G - FDC on left; carry dogC|FDG - chicken on left; carry nothing backFC|DG - FC on left; carry chicken across|FDCG - end stateKeep in mind that your program must perform a SEARCH through the possible move space for a solution, and you cannot have any third-party library dependencies; only what the language provides built in with its distribution.I am looking for solutions that are ELEGANT, by which I mean, short and to the point: ideally, without boilerplate or other stuff unrelated to the algorithm. This is a self-contained program and will not grow, so keep it small! Do not over-engineer it!I will submit solutions in at least Ruby and Elisp, though you are welcome to do the same. But I'd like to see a variety of languages here! Multiple submissions are fine as well. This is a fun little problem to solve.Most languages let you solve this problem in 20-30 lines of code or less.I'll take solutions through next Saturday and then do the judging in Sunday's episode.  Though of course you are all welcome to keep submitting solutions after I do the judging, and I can comment on them below.Have fun!Podcast listeners, you should participate as well!  Just head over to my YT channel to comment with your solution.NOTE:  I may update this comment with a shared link if we can find a reasonable place to do this. Maybe someone can create a subreddit or Discourse or something?

Hey folks!  Sorry this one is a day late.  I had to redact some confidential information and it took a little extra time.Today we talk about the Lisp family of languages, and how coooool they are, and how cool yoooouuu would be if you learned one or more of them.http://paulgraham.com has the essays I mentioned in the talk.  Enjoy!

Hey folks,Apologies for 2 weeks of missing podcasts.  The episode 2 weeks ago was all coding and didn't make much sense to just do the audio for.  And last week I was busy redoing my recording studio cabling and equipment.In this episode I talk about compilers:  a bit about how they work, and a lot about how useful they have been at various points in my career. They are a fun subject and it was an easy episode to record!I mentioned a book, The Essentials of Programming Languages. It's the one by Friedman, Wand et al.  I reaaally enjoyed working through this book, although I did study Scheme in other books first.I also mentioned the bare-bones user manual for my Wyvern game's autobag minilanguage:  It's at https://ghosttrack.com/autobag if you want to have a look.I hope this episode was interesting. It's a challenging topic to talk about at a high level without getting bogged down in the details.  I did a lot of editing in this episode, but it may have needed more. Let me know!