#code style

This was an egregious error and I have since realized the error of my ways.

`const` always binds to the left. As a special exception, when there is nothing to the left, it binds to the right. It would've been much more useful if a `const` on the right of everything applied to all types instead. Then `const int *` would be nice shorthand for `int const * const`, instead of being a misunderstanding trap which regularly causes people to think that `int const *` marks the pointer constant, when it actually marks the pointed-to-`int` constant.

So it was good and right that I decided to put `const` on the left of the type in C.

if(...){

it seems like the underscore looking more like a space would be a pro?

At first glance yes, I thought so too, but an identifier has the job not only of separating the words that comprise it, but also of holding them together.

Compare

foo_bar_qux abc def_ghi

foo_bar qux oui_def wbh

foo bar_qux_poo qkw_wjw

versus

foo-bar qux wuw-uwu opa

foo-bar-qux htj ana-fra

foo bar-qux eie-jkl-meh

Later, I attained wisdom, and from then on I knew that tabs were the objectively superior indentation choice versus spaces.

names_with_underscores

are objectively more readable than

namesWithMixedCase

and you can easily prove this to yourself by taking a long break from regularly reading each one in turn, and then getting used to them again.

Your return to reading underscored names is going to be almost effortless and instantaneous, no matter how long it has been since you last read them.

Some people like to put the operators at the end of the row, like this:

String message = "This is a string that " + "conveys no meaning and avoids being " + "a simple Lorem Ipsum because why not."; if (coordinateX > 50 && coordinateX < 100 && coordinateY > 50 && coordinateY < 100 && coordinateZ > 50 && coordinateZ < 100) {

which is common.

But I like to put the operators at the beginning of the row, like this:

String message = "This is a string that" + " conveys no meaning and avoids being" + " a simple Lorem Ipsum because why not."; if (coordinateX > 50 && coordinateX < 100 && coordinateY > 50 && coordinateY < 100 && coordinateZ > 50 && coordinateZ < 100) {

As I discovered as soon as my coworkers enabled tracing in production, regular expressions may become bottlenecks if they are complex enough.

I will show you a way to format such a complex regular expression, before you replace it with somewhat simpler. Just use empty string concatenation, like so:

String regEx = "\[TAG\] Created (" + "(access (" + "" + "token" + "" + "|code" + "))" + "|(autorization code)" + "|(device (" + "" + "token" + "" + "|code" + "))" + " for request";

Much clearer, no? Beautiful. Now be a grown-up and replace it with: