Rule #24 - Shared code ownership is the goal

YouTube recently introduced me to the channel "10 Minutes with Coach Joe." it's fantastic! I'm so excited about this material that I've added a short URL for it: MattPayne.org/cj.

Rule #24 - Shared code ownership is the goal:

"Silos of code knowledge are bad. Get to the point where you can change someone's code and they can change your code. It's our code."

The video has a nice list of major topics with timestamps. I'm very optimistic about shared code ownership.

I'm putting rule #24 at the top of this post because following the rules Coach Joe talks about is one way to achieve shared code ownership and a positive culture.

Here are the videos I'm looking forward to watching in the future:

• Rule #1: Utilize the 5 SOLID principles
• Rule #2: Utilize the 3 laws of TDD
• Rule #3: Use meaningful class names
• Rule #4: Use meaningful method names
• Rule #5: Use meaningful variable names
• Rule #6: A class should do only one thing
• Rule #7: A method should do only one thing
• Rule #8: Unit tests should always make at least 1 assert
• Rule #10: No hard coded values
• Rule #11: No duplicate code
• Rule #12: Avoid unnecessary comments
• Rule #13: The class should contain a small number of methods and lines of code
• Rule #14: Methods should have few if any parameters
• Rule #15: Avoid long if statements
• Rule #16: Avoid the switch statement
• Rule #19: Run all unit tests frequently
• Rule #20: Objects must be easy to create
• Rule #21: No type or scope definitions in variable names
• Rule #22: Methods should have very few lines of code
• Rule #23: Methods should never return null
• Rule #24: Shared code ownership is the goal
• Rule #25: Avoid nested if/else blocks
• Rule #26: Code should be formatted and readable
• Rule #29: Unit tests should never be marked with an Ignore attribute
• Rule #30: Do not test several method calls in a single unit test
• Rule #31: Avoid generating technical debt
• Rule #32: Use the proper for loop
• Rule #34: Understand the difference between an object and a data structure
• Rule #35: Try for 100% code coverage
• Rule #37: Boolean parameters should not be passed to methods
• Rule #39: Bad code is difficult to test and maintain
• Rule #40: Test code you write for happy and unhappy paths
• Rule #41: Errors should be caught, not hidden
• Rule #42: Do not test infrastructure, frameworks or libraries
• Rule #43: Null parameters should not be passed to methods

A list of videos with links

• Rule #1 - Utilize the 5 SOLID principles
• Rule #3 - Use meaningful class names
• Rule #4 - Use meaningful method names
• Rule #6 - A class should do only one thing
• Rule #7 - A method should do only one thing
• Rule #10 - No hard coded values
• Rule #12 - Avoid unnecessary comments
• Rule #14 - Methods should have few parameters
• Rule #15 - Avoid long if statements
• Rule #16 - Avoid the switch statement
• Rule #23 - Methods should never return null
• Rule #24 - Shared code ownership is the goal
• Rule #37 - Boolean parameters should not be passed to methods

---

Tags: programming, culture

← Back home