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

It’s called speed of lobsters

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

Once every 50 years or so

If my cooking senses are right, it would be like cooking bacon in a stainless steel pan, which is sticky and burny but not impossible

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?

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

Still not enough, or at least pi is not known to have this property. You need the number to be “normal” (or a slightly weaker property) which turns out to be hard to prove about most numbers.

Bitcoin is more widely seen as a vehicle for speculation rather than a decentralized currency. Unlucky.

There’s a spectrum between architecture/planning/design and “premature optimization.” Using microservices in anticipation of a need for scaling isn’t premature optimization, it’s just design.

Well, we knew he was a shitbag beforehand, so that’s not really what’s in question