Kogasa

Yeah. Normal whoppers are crunchy. 1 in 4 whoppers is soggy and chewy and hard to eat

Whoppers are good but the risk of getting a bad one is not worth it. Ech

No other country even makes the first page

If every state in America were only 1% worse than every other country, then again the first 50 entries would be the American states. This is barely saying more than “America has the highest incarceration rate,” so it shouldn’t be a surprise.

Status 200 for errors is common for non-REST HTTP APIs. An application error isn’t an HTTP error, the request and response were both handled successfully.

There may be a need for additional information, there just isn’t any in these responses. Using a basic JSON schema like the Problem Details RFC provides a standard way to add that information if necessary. Error codes are also often too general to have an application specific meaning. For example, is a “400 bad request” response caused by a malformed payload, a syntactically valid but semantically invalid payload, or what? Hence you put some data in the response body.

This should be done with font ligatures, not replacing character combinations with other characters that can’t be typed normally

Don’t think it saves bandwidth unless it’s a DNS level block, which IT should also do but separately from uBO

No, it isn’t

You’re making assumptions about the control flow in a hypothetical piece of code…

What you’re saying is “descriptive method names aren’t a substitute for knowing how the code works.” That’s once again just a basic fact. It’s not “hiding,” it’s “organization.” Organization makes it easier to take a high level view of the code, it doesn’t preclude you from digging in at a lower level.

No, your argument is equally applicable to all methods. The idea that a method hides implementation details is not a real criticism, it’s just a basic fact.

No, not “almost every modern developer thinks inheritance is just bad.” They recognize that “prefer composition over inheritance” has merit. That doesn’t mean inheritance is itself a bad thing, just a situational one. The .NET and Java ecosystems are built out of largely object-oriented designs.

You realize this is just an argument against methods?

Java is a fine choice. Much prefer it over pseudocode.

It’s possible to have an equiangular quadrilateral, i.e. whose sides are geodesics (the analogue of “straight line” on a sphere). The Gauss-Bonnet theorem implies their total interior angle is greater than 2pi, so four right angles can’t work.

Here’s an interactive demo of quadrilaterals on the sphere: https://geogebra.org/m/q83rUj8r

Notice that each side is a segment of a great circle, i.e. a circle that divides the sphere in half. That’s what it means for a path to be a geodesic on the sphere.

Good point. Four equal angles, then, although they will each have to be greater than 90 degrees.

Four right angles.

I have read programs a lot shorter than 500 lines which I don’t have the expertise to write.

I worked with Progress via an ERP that had been untouched and unsupported for almost 20 years. Damn easy to break stuff, more footguns than SQL somehow

That’s the “naughty” guy from Courage the Cowardly Dog