I forgot about the no comments rule. Yeah, that sounds insane.

Here is some sample Java code to demonstrate:

    > try {
    >     FileReader reader = new FileReader("file.txt");
    >     // Use 'reader' here.
    > } catch (FileNotFoundException e) {
    >     // ...
    > }

    > To circumvent this, a lot of exception languages are written in a more defensive style.

    > brittle in the case of C#

Here is a quote that I found:

    > For most healthy adults, up to 400 milligrams of caffeine a day—about four 8-ounce cups of brewed coffee or 10 cans of cola—is considered safe and not linked to negative health effects, according to the U.S. Food and Drug Administration (FDA).

"I put 7.3kw of panels on our roof for a $8k interest free loan and a $5k rebate."

    > The price of power is also pre approved to increase a minimum of 5% a year every year here, so the savings will be more than that.

    > As a side note, perhaps Australia perhaps has the most open and transparent electricity market in the world?

How do you know so much about the Australian power grid? Is it a hobby (personal interest) or profession-related?

    > This works best in areas where cloud cover is consistently low, so solar power doesn't vary much from day to day. That's most of Australia.

    > The large PRs needed to be large because they were adding features that couldn't be half-pregnant.

"If there is a will, there is a way."

    > Clean Code [U]ncle Bob style

In my experience, the best was to ensure your code will be approved (ok, maybe some minor tweaks) is to assign a code reviewer before you start writing code. You (the coder) performs some quick analysis, then formulates a plan for how to fix the bug or implement a change or new feature. You verbally discuss this plan using screenshare (or side-by-side in-person) so both of you can see the code that will be changed. The code reviewer needs to verbally approve your plan. This way, you don't spend a lot of time writing code and tests, only to have the reviewer rejected it very quickly: "You should have done it this way instead." (Please note: That process that I described is intentionally informal, casual, and unrigid. Why? This grants permission for the coder and reviewer to decide the plan as intelligent adults, not as "Children of JIRA" [hint: unnecessary formality].)

Another thing that I do: After I write the code, but before I write tests, I ask the reviewer to review, but not approve. After looking at their comments, I quickly add another commit to the PR to address their concerns, then start work on the tests. When the reviewer does the final review, it is very quick, like 10% of the initial review. All of this really helps to reduce coder/reviewer friction, and nearly eliminate "Tyranny of the Reviewer". One last gripe about code reviewing: It hardly makes sense for someone much more junior than the coder to do the review. I have seen this too many times.

Weirdly, I cannot copy text from that page. What am I doing wrong?

Regardless, here is the result summary:

    > Higher coffee intake groups showed lower total and visceral fat and higher skeletal muscle mass, while BMI was comparable across groups. Inverse correlations were observed between coffee intake and circulating branched-chain amino acids (BCAAs) in both sexes. In men, higher coffee intake correlated with a more favourable glucose-insulin profile. Multivariable-adjusted models revealed a distinct hormonal pattern: positive associations with total testosterone (β = +0.29 nmol/L per cup/day), bioavailable testosterone, and sex hormone-binding globulin (SHBG), alongside inverse associations with free testosterone and the free androgen index (FAI). In women, hormonal associations were more limited, with positive associations for SHBG and inverse associations for free testosterone and FAI.

Really, this will have no meaningful impact on your health. It is widely discussed by TRT (testosterone replacement therapy) doctors that supplements that can increase your total test by 100ng/dL will have no meaningful impact. Literally, you need to drink 12 cups of coffee per day to get a ~100ng/dL improvement. You are going to have a lot of second order effects from drinking 12 cups of coffee per day! I would never recommend it.

    > But more importantly, specifically Chinese fishing vessels aren’t exactly innocent either. They go dark to go and fish in waters where fishing isn’t allowed including eco sensitive zones.

    > not-Chinese sardines