You must have exceptionally competent first-level support.

I thought Ubisoft was known for their shitty launchers.

A text editor that doesn’t assume that the keys on my keyboard are in the same order as yours.

Honestly, I find it great that Linus still manages the Kernel after all this time.

It might simply be over-exertion. I get cramps when I walk a lot. Maybe your resting position already includes tension in your calves?

Apparently the link between magnesium deficiency and cramps is shaky.

magnesium supplementation compared to placebo for treating idiopathic rest cramps […] Did not significantly reduce cramp frequency

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8020016/

Are all public clocks in the US digital clocks? Off the top of my head, I can tell you 4 locations within walking distance that have analog clocks, one of them being the train station.

Back on the bad, old site, someone hypothesized that enough people tripped over that thing when it was covered by snow that it finally got moved to the side.

Aww. I confused “communities” for “instances” when I read the title. Thanks for pointing it out.

https://screenshot.help

Your data quality is questionable. You list only 2 communities for feddit.org. Lemmy Explorer has 148. I doubt that they’re all ‘suspicious’. And if they are, then that flag is itself suspicious.

Please avoid any and all situations in which you might have the chance of handling any kind of categorized data, for the sake of all of us.

I never knew that Hertz requires a periodic event. Thanks for that and the Becquerel explanation!

TIL about dpt

Tell me you don’t [Edit: need] glasses without telling me you don’t need glasses :D

That’s interesting. Obviously, you’d put a center dot to disambiguate millihertz from meter-hertz, but I can’t recall ever having learned a rule about that. So some combinations of units are inherently ambiguous?

Also: Hz/dpt.

You could only not mark a review as helpful. You couldn’t provide context if the reviewer didn’t allow comments.

There are no inherent “rules” to language, either, but when you don’t followthemthingsgetmessyandyou’reannoyingforeveryoneelese.

Thank you for linking the blog posts. They are a really good deterrent from Clean Code. I once thought I’d read it, but Fowler’s advice really is stupid.

In case you’re wondering why I replied three times: “Do one thing” :)

Exceptions are just bad. They are a separate, hidden control flow that you constantly need to be wary of. The name itself is a misnomer in my opinion, because they’re rarely exceptional: errors are not just common, but an integral part of software development

They may be a part of software development, but they should not be common during the normal execution of software. I once read the hint, “if your app doesn’t run with all exception handlers removed, you are using exceptions in non-exceptional cases”.

Throwing an exception is a way to tell your calling function that you encountered a program state in which you do not know how to proceed safely. If your functions regularly throw errors at you, you didn’t follow their contract and (for instance) didn’t sanitize the data appropriately.

Errors as values are much clearer, because they explicitly show that a function may return an error and that it should be handled.

I disagree here. You can always ignore an error return value and pretend that the “actual” value you got is correct. Ignoring an exception, on the other hand, requires the effort to first catch it and then write an empty error handler. Also (taking go as an inspiration), I (personally) find this very hard to read:

res, error = try_something()
if error {
  handle_the_error(error)
  return_own_error()
}
res2, error2 = try_something_else(res)
if error2 {
  handle_other_error(error2)
  return_own_error()
}
res3, error3 = try_yet_something_else(res2)
if error3 {
  handle_the_third_error(error3)
  return_own_error()
}
return res3

This code mingles two separate things: The “normal” flow of the program, which is supposed to facilitate a business case, and error handling.

In this example, on the other hand, you can easily figure out the flow of data and how it relates to the function’s purpose and ignore possible errors. Or you can concentrate on the error handling, if you so choose. But you don’t have to do both simultaneously:

try {
  res = try_something()
  res2 = try_something_else(res)
  res3 = try_yet_something_else(res2)
  return res3
} catch (e) {
  // check which error it is and handle it appropriately
  throw_own_exception()
}