styleguide

It's memory safe, but it's not necessarily free of race conditions! It's not only C extensions that release the GIL, the Python interpreter itself releases the GIL after a certain number of instructions so that other threads can make progress. See https://docs.python.org/3/library/sys.html#sys.getswitchinte.... Certain operations that look atomic to the user are actually comprised of multiple bytecode instructions. Now, if you are unlucky, the interpreter decides to release the GIL and yield to another thread exactly during such instructions. You won't get a segfault, but you might get unexpected results. See also https://github.com/google/styleguide/blob/91d6e367e384b0d8aa...

I think the Google Go style guide is really nice and pragmatic. There are some references to the GoTips for some advanced subjects. I hope they release it someday. I made an issue for it: https://github.com/google/styleguide/issues/881

Since it's been around since 2003, I'm curious to know how many projects out there are using it. Would be great if there are some open source examples available as well. I mostly stick to Python, so I'm most familiar with the Google docstring format[1], but seeing as there are other ones[2] as well aren't those usable for other languages too? Seems to be the case of yet another "standard", though since this is such an old project I may out of my depth in saying that. --- [1]: https://github.com/google/styleguide/blob/gh-pages/pyguide.m... [2]: https://stackoverflow.com/a/24385103

> Honestly, excessive cleverness does not generally pass code review @ Google. And yet the Google style guide literally says: "Assume the person reading the code knows Python better than you do." https://github.com/google/styleguide/blob/gh-pages/pyguide.m...

I have read about this: https://github.com/google/styleguide/tree/gh-pages/cpplint There is also this: https://github.com/mre/awesome-static-analysis

Funny that the page recommending that we not use <head> still uses <head>. "Do as we say. Not as we do." You can view source, and they post it to GitHub. https://github.com/google/styleguide/blob/gh-pages/htmlcssgu...

While supported, list comprehensions that are multiple levels deep isn't considered good style. There is an example of this in Google's python style guide: https://github.com/google/styleguide/blob/gh-pages/pyguide.m...

I don't see how anyone could have a hard time using lambdas... they've been around forever, and most programming languages nowadays have them. A good rule of thumb is given by the google python coding guidelines [1]: "Okay to use them for one-liners. If the code inside the lambda function is any longer than 60-80 chars, it's probably better to define it as a regular (nested) function." [1] https://github.com/google/styleguide/blob/gh-pages/pyguide.m...

https://developers.google.com/edu/python/introduction: According to the official Python style guide (PEP 8), you should indent with 4 spaces. (Fun fact: Google's internal style guideline dictates indenting by 2 spaces!) https://github.com/google/styleguide/blob/gh-pages/pyguide.m...: Indent your code blocks with 4 spaces.

Unless companywide guidelines are agreed upon, and published. E.g http://google.github.io/styleguide/javaguide.html https://github.com/google/styleguide/blob/gh-pages/pyguide.m...

The only recommendation for users is "you should avoid reusing the same password across multiple different sites. A password manager like 1Password or LastPass can help with this." Seriously? No help to tell me if I have been affected? If someone here knows a JS linter that does not require npm/yarn, even ten times less powerful than eslint, please share. It's astonishing that linting C++ requires one file, https://github.com/google/styleguide/blob/gh-pages/cpplint/c..., but linting JS requires MBs of dependencies.

Not exactly language-agnostic, nor about programming per se, nor a book, but [Google Style Guides](https://github.com/google/styleguide) offer a lot of specific, opinionated, practical advice that you can apply immediately. It's like an MLA manual for programmers.

Here's the direct github link if you want to fork or star: https://github.com/google/styleguide/blob/gh-pages/htmlcssgu...