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
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.
I have read programs a lot shorter than 500 lines which I don’t have the expertise to write.
This has nothing to do with Windows or Linux. Crowdstrike has in fact broken Linux installs in a fairly similar way before.
Sure, throw people in jail who haven’t committed a crime, that’ll fix all kinds of systemic issues
Catch and then what? Return to what?
Okay, but this makes more sense as an instance method rather than a static one
Instance properties are PascalCase.
Yeah, properties (like a field but with a getter and/or setter method, may or may not be backed by a field) are PascalCase
That’s an instance property
Yes, with Iosevka font
U good?
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.