Jumping into an existing codebase
source link: https://changelog.com/gotime/307
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Brought to you by
Jumping into a codebase you’re unfamiliar with can be challenging. Are there better & worse ways to go about it? In this episode, Ian gathers a panel (Johnny, Kris & Jon) to discuss the ins & outs of familiarizing yourself with an existing codebase.
- 87 minutes
- Recorded Mar 6, 2024
- Published Mar 12, 2024
- Download (84MB)
- Transcript
- 🎧 3,170
Featuring
Sponsors
Changelog News – A podcast+newsletter combo that’s brief, entertaining & always on-point. Subscribe today.
Fly.io – The home of Changelog.com — Deploy your apps and databases close to your users. In minutes you can run your Ruby, Go, Node, Deno, Python, or Elixir app (and databases!) all over the world. No ops required. Learn more at fly.io/changelog and check out the speedrun in their docs.
Chapters
| 1 | 00:00 |
It's Go Time! |
| 2 | 00:44 |
Meet the co-hosts |
| 3 | 01:26 |
Tests |
| 4 | 07:26 |
Assume the documentation is bad |
| 5 | 12:00 | |
| 6 | 13:51 |
Consulting |
| 7 | 17:15 |
Using your mouse |
| 8 | 18:03 |
Quality of tests |
| 9 | 27:08 |
Acronyms |
| 10 | 28:03 |
Lack of comments |
| 11 | 35:51 |
When things aren't ideal |
| 12 | 39:04 |
An archivist |
| 13 | 48:03 |
Consistency vs improvements |
| 14 | 53:39 |
What if there are no tests? |
| 15 | 55:22 |
What if it's not testable? |
| 16 | 56:08 |
Mitigating risk |
| 17 | 1:03:31 |
Rewrites |
| 18 | 1:14:30 |
Unpopular opinions! |
| 19 | 1:15:05 |
Kris' unpop |
| 20 | 1:21:44 |
Johnny's unpop |
| 21 | 1:26:30 |
Outro |
Transcript
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK