YAGNI

Detailed commit messages w/ Chris Toomey

Nov 1, 2022

53:03

Creator website

Highlights

AI Chapters

Episode notes

Communication Is a Critical Skill for Software Developers

02:41

GitHub

04:26

How to Write Good Get Commit Messages

01:49

Introduction

2min

Do We Really Need This?

2min

Git - Is That Really True?

2min

Git History Collapses Every So Many Times

2min

Is There a Value in Capturing History in Commits?

2min

Is It Worth the Effort to Produce This Lengthy Commit Message?

2min

Laravel

3min

The Seven Rules of a Great Get Commit Message

3min

The Third Most Important Rule of a Great Commit

3min

10.

How to Write Good Get Commit Messages

2min

11.

GitHub Markdown

2min

12.

GitHub

4min

13.

Are You Approaching Senior Developers?

4min

14.

Commit Messages or Code Comments?

2min

15.

Code Commit Messages

2min

16.

The Importance of Committing Good Commit Messages

2min

17.

Communication Is a Critical Skill for Software Developers

3min

18.

Is It a Good Idea to Have a Developer?

2min

19.

Is RTFM a Trope?

2min

20.

The Next Generation of Commits Isn't Going to Work, but Is It?

2min

21.

Commit Messages as a Best Practice

2min

22.

Tests

5min

Chris Toomey on Twitter
Matt Swanson on Twitter

Arrows
Sagewell Financial

Write Good Commit Messages by Blaming Others
The seven rules of a good git commit message
David Hemphill - WIP
Hot Ones
Russian Roulette and expected value

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.