Long Names Are Long – journal.stuffwithstuff.com
One smart thing Google does is rigorous code reviews. Every change, before you can land it, gets reviewed in at least two ways. First, someone on the team does a normal review to make sure the code does what it’s supposed to.
Long Names Are Long One smart thing Google does is rigorous code reviews. Every change, before you can land it, gets reviewed in at least two ways. First, someone on the team does a normal review to make sure the code does what it's supposed to. But, then, there's a second layer of review called readability . It makes sure the code is, well, readable: Is it easy to understand and maintain? Does it follow the style and idioms of the language? Is it well-documented? Dart usage inside Google is cranking up, so I've been doing a ton of these kind of code reviews. As a language designer, it's fasci
related reading
- Cognitive load is what mattersminds.md
- Naming Things in Code - journal.stuffwithstuff.comjournal.stuffwithstuff.com
- Function Lengthmartinfowler.com
- Write code that is easy to delete, not easy to... — programming is terribleprogrammingisterrible.com
- Essays on programming I think about a lot | benkuhn.netbenkuhn.net
- Ninja codejavascript.info
- Writing Better Go: Lessons from 10 Code Reviews - Speaker Deckspeakerdeck.com
- Writing Better Go: Lessons from 10 Code Reviews - Speaker Deckspeakerdeck.com
- Mistakes I see engineers making in their code reviewsseangoedecke.com
- styleguide | Style guides for Google-originated open-source projectsgoogle.github.io
- Why Good Developers Write Bad Unit Tests · mtlynch.iomtlynch.io
- Every layer of review makes you 10x slowerapenwarr.ca