076: Ben Needs A MinuteShow Details57min 39s
075: What Problem Does This Solve?Show Details49min 27s
074: What's On Your Workbench?Show Details58min 19s
073: Our Golden ParachuteShow Details37min 2s
072: Too Many HatsShow Details57min 31s
071: Potluck #4Show Details1hr
070: Self ReflectionsShow Details44min
069: Now I'm Catching EventsShow Details38min 27s
068: Hire Women, Inspire WomenShow Details1hr
067: We Have Feelings On LoggingShow Details38min 41s
066: Make Meetings Suck LessShow Details46min 58s
065: TDD In the Trenches with Scott StrozShow Details41min 47s
064: Should I Stay Or Should I Go?Show Details40min 9s
063: Nobody Makes It Out Alive!Show Details33min 20s
062: Note To SelfShow Details1hr 8min
061: Software Is For PeopleShow Details51min 11s
060: Technical DebtShow Details1hr
059: Everything Old Is New AgainShow Details54min 45s
058: Do 10x Developers Exist?Show Details53min 27s
057: Goals for 2022Show Details54min 40s
056: Best of 2021Show Details1hr 8min
055: Sales FailsShow Details50min 25s
054: We're So QuackedShow Details41min 41s
053: Product Management with Adam LehmanShow Details39min 18s
052: Starting Your Own Business, with Steve RittlerShow Details1hr 15min
051: You Are ReplaceableShow Details36min 31s
050: Where Do You See Yourself in 5 Years?Show Details52min 49s
049: Revisiting Replatforming - There Is No Correct AnswerShow Details49min 31s
048: // TODO: Microwave ToDo ListShow Details56min 17s
047: Email Ruins EverythingShow Details56min 2s
046: Secrets Management vs. Premature OptimizationShow Details44min 15s
045B: The AftershowShow Details24min 43s
045: Join Our DiscordShow Details10min 57s
044: Facebook's No Good Very Bad WeekShow Details55min 5s
043: Relay Race ProgrammingShow Details50min 8s
042: Potluck #3Show Details51min 53s
040: Automaticity Is a Weird WordShow Details41min 59s
039: Ben's Future at InVisionShow Details51min 54s
038: Holding Developers AccountableShow Details57min 54s
037: Brian Klaas Talks CloudShow Details1hr 17min
036: Blogs and Digital GardensShow Details58min 32s
035: Being a Swamp GuideShow Details47min 39s
034: Some of My Best Friends Are React Developers!Show Details44min 18s
033: Software PatentsShow Details42min 35s
032: What Comes After Senior Developer?Show Details49min 52s
031: To The Cloud! But Why?Show Details1hr 1min
030: Carol's Consult Catch-Up ConversationShow Details48min 34s
029: Potluck #2Show Details46min 8s
028: Buy vs. DIYShow Details47min 30s
027: Giving Technical PresentationsShow Details34min 15s
026: PasswordsShow Details59min 6s
025: Breaking Up With Your StackShow Details1hr 1min
024: The Archetype of an Effective DeveloperShow Details1hr 25min
023: Book Club #1 Clean Code by "Uncle Bob" Martin (pt2)Show Details1hr 6min
022: Book Club #1 Clean Code by "Uncle Bob" Martin (pt1)Show Details1hr 11min
021: Listener Questions #2Show Details1hr 21min
020: Carol Needs a ConsultShow Details58min 15s
019: MakefilesShow Details1hr 15min
018: Feature Flags (Finally!)Show Details1hr 25min
017: Premature OptimizationShow Details53min 47s
016: InterviewingShow Details1hr 16min
015: Potluck #1Show Details1hr 22min
014: Zen and the Art of Pull RequestsHide Details1hr 12min
1hr 12minPublished Mar 17, 2021 at 11:00am
Ben has "feelings" about many aspects of web application development. And, after working with git and GitHub for the last 10-years, he's formed a lot of strong opinions - oftentimes strongly held - about how Pull Requests (PRs) should be created and managed within a team context. For example:
Code completed is more important than code being written. As such, if an open PR sits around for more than an hour, your team has failed to review said PR in a timely manner.
If a PR takes more than 15-minutes to review, the PR is too large. The author of said PR has failed to decompose the problem into smaller, independently-deployable changes.
As you can imagine, Ben's "PR Commandments" don't work for every one or every team. This week, the crew meets to discuss his approach to Pull Requests, reaching consensus on some concepts and pushing-back strongly on others. And, of course, this is totally fine - every team has its own set of constraints that have bearing on how that team operates. Your mileage my vary!
Plus, we find out that Carol can be bribed with tacos... sweet, sweet tacos!
Triumphs & Failures
- Adam's Triumph - He just had his 9-year work anniversary at AlumnIQ! And, as he reflects on the last 9-years, he's amazed to realize that he never wanted to quit. Every day seems to be a stream of challenges; which is exactly what makes the work so invigorating! When he thinks back to prior jobs that he has quit, they were always boring jobs building "forms over data" type products. He's looking forward to the next 9-years!
- Ben's Triumph - He gets a little nostalgic this week, recalling a thought he had 15-years ago about how amazing it would be to create a software system that worked like the human body, with cells that acted independently and communicated via hormones. At the time, he dismissed the thought as being crazy; but, fast-forward to today, it turns out that his instincts were actually spot-on. Though, instead of hormones, we have event-streams, message queues, and pub-sub mechanism; and, instead of cells, we have distributed, independently-scalable systems that are kept up-to-date through "eventually consistent" communications!
- Carol's Triumph - Her team has moved all thirteen of their pending-work branches into testing. This is the culmination of weeks of hard work. And, to top it off, she's proud of the fact that she was able to buckle-down and maintain a high standard of quality for her coding all the way to the very end! No cutting corners for this engineer!
- Tim's Triumph - He was required to participate in a coaching and mentoring workshop at his company. And, though he was initially frustrated about having to put pressing-work-matters on hold, once the workshop started, he found it be quite helpful. And, he was even able to find the solution to a problem he's been wrestling with for some time! It turns out that if you open yourself up to opportunities in front of you, you never know what you're gonna find!
Notes & Links
- git - the most popular source-control system on planet earth.
- GitHub - a very popular source-control solution, built on git.
- BitBucket - another popular source-control solution from Atlassian.
Follow the show! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes weekly on Wednesday.
And, if you're feeling the love, support us on Patreon.
013: Do What You Love And You'll Never Work A Day In Your LifeShow Details46min 51s
012: Idiomatic CodeShow Details42min 3s
011: Listener Questions #1Show Details1hr 10min
010: ScalingShow Details1hr 9min
009: TestingShow Details58min 13s
008: Origin Stories Pt 2Show Details1hr 11min
007: Origin Stories Pt 1Show Details58min 5s
006: Hopes for 2021Show Details57min 13s
005: Monolith vs. MicroservicesShow Details42min 44s
004: Impostor SyndromeShow Details1hr 18min
003: Burnout, Mental Exhaustion, and ProductivityShow Details1hr 4min
002: Working from homeShow Details54min 24s
001: Adam's Secret ShameShow Details1hr 8min
000: Hello, World!Show Details8min 4s