coding-style | Our preferred formatting style and best practices | Code Analyzer library

One of my tasks is to analyze source code. The chunks that usually takes the most time to be understood are those where the developer uses confusing terms for variables or methods, like...

• myfavoritething=json.dumps(url) (what is this variable? what is the purpose? apparently the user is encoding the url for some dark purpose...)
• public void getName(values, result) { ... (this was not a getter, the function has no return value, but it calculates a result from the input values)
• POST /loadService (which does not load something, just returns a lot of variables)

Given that this is a quite common issue, is there a technical term for this coding-style bad habit?

I'm trying to skill up on JSDoc, and I have this method:

Is there an easy way of removing blank lines from IPython notebook?

I have picked up a habit of blank lines from web development and my fingers tend to hit enter automatically. This makes IPython notebooks less(by taking too much of my 14" screen), not more readable in most cases.

I was wondering if there is a way of automatically remove blank lines from the notebooks.

In notebooks, I think preferred way of splitting the code is by placing each separate method to a different cell.

Is commonly accepted style guide for notebooks or does PEP 8 apply as it is?

EDIT: I think question 2, Is answered by IPython docs. https://github.com/ipython/ipython/wiki/Dev:-Coding-style

I have a class with a probably unnecessarily cumbersome name, that contains a lot of static methods I use elsewhere.

Rather than fill my code with a lot of

In javax.imageio.ImageIO there is a method #write(RenderedImage im, String formatName, OutputStream output) that accepts a "stringly-typed" format developer wants image to be written to.

There is an inner class called CanEncodeImageAndFormatFilter deep inside that file that checks if there is an SPI (whatever it is) that supports the aforementioned format. For example, BMPImageWriterSpi declares

Following these guidelines (and almost any other), functions and var names should use lowerCamelCase while Class (and c'tors) names should use UpperCamelCase.

I've looked for an ESLint rule to enforce this convention but the closest I've found is id-match which doesn't seem to distinguish between function, var, or class.

Is there a better rule? Should I be using the id-match rule along with new-cap rule? (feels dirty)

Lets assume, we have an operation based on some file, connection, or other resource.

We need a method, which can be run with provided resource, or - if not provided - creates own:

The following program does not work on non-GUI environments. I want to let this program save the figure to a temporary png file when plt.show is called.

Google c++ coding-style does not allow non-trivial static objects (and for a reason) and hence no singletons. At the same time singletons do represent reality of application logic.

So what is the correct way to implement singleton functionality google-style:
(a) have static pointers and initialize them on startup as a separate step (e.g. by linked list of initializer/maker classes)
(b) have context holding references to all singleton-like object and pass it with every method (c) have context to be member of every class
(d) something else?