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 can be, usually for college credit though

At the universities I went to, Calc 2 was integration, sequences and series, then Calc 3 was multivariable. They really pack all the harder parts into 2.

I got that banana for my cat. I think the catnip wears off or something but he still likes to have it near him.

It’s called speed of lobsters

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

It’s a reach, but the Fourier transformation of a Schwarz (rapidly decaying) function is also a Schwarz function. Compact support is a strictly stronger condition than Schwarz (the function must eventually decay to 0) but doesn’t have this nice property with respect to Fourier transforms, i.e. the FT of a compactly supported function is Schwarz but not necessarily compactly supported

You look like you could turn runes into strength

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.

Eddie Bauer and Carhartt are my go-tos. Both carry tons of tall sizes. Wrangler has some too and may be cheaper.

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?