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
Explore this link on the map →related reading
- Ninja codejavascript.info
- Reading 4: Code Reviewweb.mit.edu
- Naming Things in Code - journal.stuffwithstuff.comjournal.stuffwithstuff.com
- Writing Better Go: Lessons from 10 Code Reviews - Speaker Deckspeakerdeck.com
- Writing Better Go: Lessons from 10 Code Reviews - Speaker Deckspeakerdeck.com
- Cognitive load is what mattersminds.md
- Function Lengthmartinfowler.com
- GitHub - johnousterhout/aposd-vs-clean-code: A discussion between John Ousterhout and Robert Martin about differences between John's book "A Philosophy of Software Design" and Bob's book "Clean Code". · GitHubgithub.com
- styleguide | Style guides for Google-originated open-source projectsgoogle.github.io
- Clean up your code: How to create your own C# code styleblog.unity.com
- Package names - The Go Programming Languagego.dev
- styleguide | Style guides for Google-originated open-source projectsgoogle.github.io