Twelve Ways to Make Code Suck Less

Twelve Ways to Make Code Suck Less

Devoxx via YouTube Direct link

Prefer Clear Code over Clever Code

9 of 18

9 of 18

Prefer Clear Code over Clever Code

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Twelve Ways to Make Code Suck Less

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Intro
  2. 2 Why should we care about code quality?
  3. 3 What's Quality Code?
  4. 4 Schedule Time to Lower Technical Debt
  5. 5 What Causes Technical Debt?
  6. 6 Favor High Cohesion
  7. 7 Think about frequency of change
  8. 8 Favor Loose Coupling
  9. 9 Prefer Clear Code over Clever Code
  10. 10 Apply Zinsser's Principle on Writing
  11. 11 Write Expressive Self-Documenting Code
  12. 12 Avoid Long Methods-Apply SLAP
  13. 13 Perils of Long Methods
  14. 14 How long is long?
  15. 15 Turns out long is not about length of code, but levels of abstraction
  16. 16 Variable Names Represent Abstractions
  17. 17 Facilitating Tactical Code Reviews
  18. 18 Reduce State & State Mutation

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.